Custom clients and SDKs

The connection contract

Generic configuration

Most MCP capable applications take one of these shapes. Only the key name varies between them: url, serverUrl, or a type of http.

{ "mcpServers": { "glitch": { "url": "https://mcp.glitchads.ai/mcp" } } }

// headless: add the header, and reference the key from the environment
{
  "mcpServers": {
    "glitch": {
      "url": "https://mcp.glitchads.ai/mcp",
      "headers": { "Authorization": "Bearer ${GLITCH_API_KEY}" }
    }
  }
}

Python

# pip install "mcp>=2"
import asyncio
import os

import httpx2
from mcp import Client
from mcp.client.streamable_http import streamable_http_client

async def main():
    headers = {"Authorization": f"Bearer {os.environ['GLITCH_API_KEY']}"}
    async with httpx2.AsyncClient(headers=headers, timeout=httpx2.Timeout(30, read=300)) as http:
        transport = streamable_http_client("https://mcp.glitchads.ai/mcp", http_client=http)
        async with Client(transport) as client:
            tools = await client.list_tools()  # 21 glitch_* tools
            result = await client.call_tool(
                "glitch_get_performance",
                {"organization": "acme", "from": "2026-07-01", "to": "2026-07-07"},
            )
            print(result.content[0].text)

asyncio.run(main())

TypeScript

// npm install @modelcontextprotocol/sdk zod
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(
  new URL("https://mcp.glitchads.ai/mcp"),
  { requestInit: { headers: { Authorization: `Bearer ${process.env.GLITCH_API_KEY}` } } }
);

const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);

const res = await client.callTool({
  name: "glitch_run_detector",
  arguments: { organization: "acme", campaign: "acme-prospecting", detector: "no_conversion_keywords" },
});

Agent frameworks

Frameworks with MCP support take the same URL plus the Authorization header. One rule for anyone building a loop that runs on its own:

• Honour the annotations. A tool with readOnlyHint: false can change things, and destructiveHint: true marks the four that change a running campaign. Gate those behind human confirmation, or run them with dry_run: true and read the preview in code. The server side guardrails hold regardless, but your users will thank you.

Test keys (glads_test_) are not available yet, so there is no sandbox organization to build against. Until there is, use dry_run previews to check what a write would do.

If you do not need MCP semantics at all, the REST API exposes the same operations directly.

Check it worked

• tools/list returns the tools.
• glitch_list_organizations returns the organizations the connection covers, with your role in each; every other tool that takes organization requires it.
• An unauthenticated request returns 401 with a WWW-Authenticate header pointing at the resource metadata, which means discovery is working.
• The tool list shows 21 tools named glitch_*.

Ask: "List my Glitch organizations." You should get back the organizations your connection covers, with your role in each.

Troubleshooting

Next

• The tool reference
• Authentication and scopes
• The REST API