Connect your client

One endpoint for everyone

https://mcp.superagnt.com/mcp

The credential you present selects the workspace, not the URL. That means this string is identical for every customer: there is no per-tenant subdomain to look up and no path to personalize, and a config block copied from a teammate connects to your workspace as soon as you sign in.

Transport is Streamable HTTP MCP: JSON-RPC 2.0 over POST, with a stream that carries tools/list_changed when the served tool set changes. Clients that cannot speak remote HTTP MCP bridge through mcp-remote over stdio, which is the "Other" block below.

Claude Code

Two pieces. The MCP server goes in as a Claude connector: open the prefilled dialog on claude.ai and click Add. It reaches Claude Code signed in with your Claude account from the next session. The plugin carries the superagnt skills, the instructions for using the tools.

/plugin marketplace add superagnt/plugins
/plugin install superagnt@superagnt

Claude Code signed in with an API key never loads connectors. There, add the server directly (connection only, no skills).

claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
claude mcp login superagnt

Every other client

Each block below is the whole change for that client. Where a config path is shown, create the file and its server map if they do not exist yet.

codex mcp add superagnt --url https://mcp.superagnt.com/mcp
codex mcp login superagnt

{
  "mcpServers": {
    "superagnt": {
      "url": "https://mcp.superagnt.com/mcp"
    }
  }
}

code --add-mcp '{"name":"superagnt","type":"http","url":"https://mcp.superagnt.com/mcp"}'

gemini mcp add --transport http superagnt https://mcp.superagnt.com/mcp

{
  "mcpServers": {
    "superagnt": {
      "type": "streamable-http",
      "serverUrl": "https://mcp.superagnt.com/mcp"
    }
  }
}

{
  "context_servers": {
    "superagnt": {
      "source": "url",
      "url": "https://mcp.superagnt.com/mcp"
    }
  }
}

https://mcp.superagnt.com/mcp

openclaw mcp add superagnt --url https://mcp.superagnt.com/mcp --transport streamable-http --auth oauth
openclaw mcp login superagnt

# ~/.hermes/config.yaml
mcp_servers:
  superagnt:
    url: "https://mcp.superagnt.com/mcp"
    headers:
      Authorization: "Bearer <YOUR_MCP_TOKEN>"

{
  "mcpServers": {
    "superagnt": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.superagnt.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_MCP_TOKEN>"
      ]
    }
  }
}

OAuth or a bearer token

OAuth 2.1 is the lead path for almost every client, because the endpoint is its own authorization server. It publishes discovery metadata, accepts dynamic client registration, and runs PKCE S256, so an OAuth-capable client needs the URL and nothing else: it registers itself, you approve once in a browser, and the client holds its own credential. The consent screen doubles as signup, so a reader without an account still lands in a working workspace.

A workspace MCP bearer token from the dashboard is the fallback for clients that cannot do OAuth, and for people who would rather paste a header. Mint one at app.superagnt.com and drop it wherever the blocks above print <YOUR_MCP_TOKEN>.

The full credential contract, including what the REST API accepts and which scopes are refused where, is on Authentication.

GUI-only clients

The Claude app, ChatGPT and Grok keep connectors in your account rather than in a file on disk. No agent can wire these for you, so the steps below are for a human: paste the endpoint into the connector form and approve the consent screen.

https://mcp.superagnt.com/mcp

https://mcp.superagnt.com/mcp

https://mcp.superagnt.com/mcp

Verify it worked

The quickest independent check is a raw tools/list. It also doubles as the plain-HTTP integration path for anything that is not an MCP client at all. The Accept header carries both content types because Streamable HTTP lets the server answer either with a JSON body or with an SSE stream: a plain tools/list comes back as JSON, while a long-running tools/call that asked for progress is streamed back as text/event-stream.

curl -sS https://mcp.superagnt.com/mcp \
  -H "Authorization: Bearer <YOUR_MCP_TOKEN>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Inside a connected client, call agnt_onboarding instead. It confirms the connection and returns the platform brief in one move.

Scoped entry points

The endpoint also answers on https://mcp.superagnt.com/mcp/<facet>. A server created now serves every curated data source whichever path you connect on: connecting through a facet for the first time provisions the workspace's default server with that facet's own tool families added, and stamps the slug so the install can be attributed to wherever it came from. A facet is an entry point, not a partition: once the server exists, your credential resolves the same server on any path. Servers created before the grouped tool list, which list one tool per operation, started scoped to their facet's families and keep that scope until you widen it, with no reconnect.

The facets match the MCP server listings: social-data, linkedin, x, instagram, tiktok, youtube, reddit, facebook, web-scraping, seo, lead-enrichment, email-finder and company-enrichment. A skill connects on the plain endpoint, and its setup guide switches on the tool families it needs.

An unregistered slug does not fail as a protocol error. It returns a structured 404 naming the valid facets, so a client that guessed can correct itself.