Connect ChatGPT, Claude & Any LLM

​

Choose your integration

​

Prerequisites

1. Dashboard setup — create an agent and copy credentials.
2. MCP URL from Agentic Stack → Overview (e.g. https://agent-kit.abstraxn.com/mcp).
3. For OAuth connectors: MCP_OAUTH_ENABLED=true on the deployment. Kong on /mcp must use a pre-function plugin to strip Bearer before key-auth (see MCP integration).

​

Path 1 — Claude Code (API key)

claude mcp add -s user web3-agent-kit https://agent-kit.abstraxn.com/mcp \
  --header "Authorization: YOUR_PER_AGENT_API_KEY"

claude --mcp-debug

​

Path 2 — ChatGPT & Claude Web (OAuth)

​

What Abstraxn exposes

​

ChatGPT

1. Settings → Apps → Advanced Settings → enable Developer Mode.
2. Create app → name it Abstraxn Agent Kit.
3. MCP server URL: https://agent-kit.abstraxn.com/mcp
4. Authentication: OAuth (ChatGPT discovers metadata automatically).
5. On first tool use, complete the Authorize redirect.
6. On the consent page, paste your per-agent API key from the dashboard.
7. Use the app in chat (e.g. /abstraxn if configured as slash command).

​

Claude Web & Desktop

1. Settings → Connectors → Add custom connector.
2. Name: Abstraxn Agent Kit
3. URL: https://agent-kit.abstraxn.com/mcp
4. Click Connect → complete OAuth consent (per-agent API key on consent form).

https://dev-agent-kit.abstraxn.com/mcp

​

OAuth scopes

​

Connector icon (Claude / ChatGPT)

​

Why you might still see an old or generic icon

1. Kong blocked /favicon.png — if the favicon URL returns 401 Key, Claude falls back to a generic MCP placeholder (colorful triangle / globe). Whitelist GET /favicon.ico and GET /favicon.png from Kong key-auth (same as OAuth discovery paths).
2. Connector cached the first icon — Claude caches connector metadata. After deploying a new favicon, disconnect and re-add the connector (or toggle off → on in the Connectors menu).
3. Client rollout — some Claude builds read logo_uri from OAuth metadata; others use /favicon.png or MCP icons[]. Abstraxn exposes all three so icons update as clients adopt each mechanism.

​

Verify branding endpoints

# Canonical favicon (200 image/png)
curl -sS -D - -o /dev/null "https://abstraxn.com/icon.png"

# OAuth metadata must include logo_uri → abstraxn.com/icon.png
curl -sS "https://agent-kit.abstraxn.com/.well-known/oauth-authorization-server" | jq '.logo_uri'

# Optional: MCP host redirect (302 → abstraxn.com/icon.png; Kong must allow GET without key-auth)
curl -sS -D - -o /dev/null "https://agent-kit.abstraxn.com/favicon.png"

​

Path 3 — Any LLM via @abstraxn/mcp-client

npm install @abstraxn/mcp-client

import { AgentKitMcpClient, mcpToolsToOpenAi } from '@abstraxn/mcp-client';

const mcp = new AgentKitMcpClient({
  serverUrl: process.env.MCP_SERVER_URL!,
  authToken: process.env.MCP_SERVER_AUTH_TOKEN!,
  defaultAgentId: session.agentKitId, // when using application API key
});

const tools = await mcp.discoverTools(); // live names from tools/list
const openAiTools = mcpToolsToOpenAi(tools);

// LLM returns tool_call → forward to MCP (use names from discoverTools only)
const toolName = tools[0].name;
const outcome = await mcp.callTool(toolName, { agent_id: session.agentKitId });

​

Streamable HTTP (2025-06-18)

• POST /mcp — JSON-RPC; returns Mcp-Session-Id on initialize
• GET /mcp — SSE heartbeat stream (optional)
• DELETE /mcp — close session

​

ERC-8004 discovery

{
  "services": [
    {
      "name": "MCP",
      "endpoint": "https://agent-kit.abstraxn.com/mcp",
      "version": "2025-06-18",
      "security": {
        "oauth2": {
          "protectedResourceMetadata": "https://agent-kit.abstraxn.com/.well-known/oauth-protected-resource",
          "scopes": ["mcp:tools:read", "mcp:tools:transfer", "mcp:tools:paid"]
        },
        "apiKey": { "header": "Authorization" }
      }
    }
  ]
}

​

Related

• MCP in Cursor
• MCP tools reference
• Troubleshooting