What is the SiteGPT MCP server?

A remote Model Context Protocol server at https://sitegpt.ai/mcp. Any MCP-aware assistant, such as Claude, connects to it, asks you to approve access in the browser via OAuth, and can then create and manage SiteGPT chatbots on your behalf.

How do I connect Claude to SiteGPT?

Open Claude’s integrations or connectors settings, add a custom MCP server, and enter https://sitegpt.ai/mcp. Claude opens SiteGPT’s OAuth approval page; review the permissions and chatbot access, click Connect, and the SiteGPT tools appear in Claude.

Why does the server expose only two tools?

By design. Instead of one tool per endpoint, the server ships a compact pair: search finds the right SiteGPT API v2 operation from the catalog, and execute calls it. The assistant composes the whole platform from those two, and your context window is not flooded with a hundred tool definitions.

Do I paste an API token into the assistant?

No. The approval page creates an OAuth grant for the AI client. During approval SiteGPT shows the app requesting access, the permissions, and whether it can reach all chatbots or only selected ones. The grant never exceeds what your dashboard role allows, and you can revoke it.

Can I run the MCP server locally instead?

Yes. npx -y @sitegpt/cli mcp runs the same server over stdio for clients that launch local processes, such as Claude Code, Cursor, and Codex. Remote and local reach the same account.

Does it work without a SiteGPT account?

Chatbot management over MCP uses your account via OAuth. To try SiteGPT with no account at all, agent-first onboarding (documented at sitegpt.ai/auth.md) lets an agent build and train a chatbot from a URL and hand back a preview-and-claim link.

Model Context Protocol

Customer support, served over MCP

SiteGPT runs a remote MCP server with browser-based OAuth. Paste one URL into Claude or any MCP-aware assistant and it can build, train, and manage your support chatbots. Nothing to install, no token to paste.

All agent surfaces →

claude — connected to SiteGPT

> List my SiteGPT chatbots, then show this  week’s unresolved conversations for Support Bot   search("list chatbots")  execute(GET /api/v2/chatbots)  → 3 chatbots  execute(GET /api/v2/conversations?status=open)  ✓ 7 open conversations, 2 waiting on a human

Agents read this page too

Two tools, the whole platform

search + execute, not a hundred tool stubs

Most MCP servers dump one tool per endpoint into your context window. SiteGPT ships a compact pair over the full API v2 catalog, so the assistant composes anything the dashboard can do without drowning in definitions.

Find the right operation

Searches the SiteGPT API v2 catalog and returns the matching operations with their parameters, so the assistant discovers capabilities instead of hallucinating endpoints.

execute

Call it, with your permissions

Runs the selected API call through an authenticated bridge. Every call is bounded by your OAuth grant: your role, your token scopes, your chatbot restrictions.

Machine-readable details live in the MCP server card and the MCP docs.

Connect in two minutes

Every MCP client, one endpoint

Remote clients connect straight to the endpoint and approve access in the browser. Local clients can run the same server over stdio via the CLI.

Claude (web & desktop)

Add a custom connector in Claude’s settings, paste the server URL, and approve access in the browser. No install, no API key.

Settings → Connectors → Add custom connector

https://sitegpt.ai/mcp

Claude Code

One command adds the remote server; the OAuth approval opens in your browser. Prefer running locally? The stdio variant works too.

add the remote MCP server

claude mcp add --transport http sitegpt https://sitegpt.ai/mcp

Cursor

Point Cursor at the remote server, or run it locally via the CLI.

.cursor/mcp.json

{
  "mcpServers": {
    "sitegpt": {
      "url": "https://sitegpt.ai/mcp"
    }
  }
}

Codex & other stdio clients

Any MCP client that launches stdio servers can run the SiteGPT server through the CLI.

~/.codex/config.toml

[mcp_servers.sitegpt]
command = "npx"
args = ["-y", "@sitegpt/cli", "mcp"]

Building on a runtime we cover? Claude Code, Cursor, Codex, OpenCLAW, and Hermes each have a dedicated guide.

Safe to hand to an agent

The approval page is the contract

OAuth grant, not a pasted token

The approval page creates a scoped grant for the AI client. You never paste an API key into an assistant, and you can revoke the grant at any time.

Role-aware by construction

The client cannot receive permissions or chatbot access your dashboard user does not have. The grant is a subset of you, never a superset.

Chatbot-level scoping

Approval shows whether the client reaches all chatbots or only the ones you select, so an assistant for one project stays inside that project.

Discoverable, not guessable

The server advertises OAuth metadata automatically and publishes a server card under .well-known, so clients negotiate the connection without manual configuration.

MCP + SiteGPT, answered

What is the SiteGPT MCP server?: A remote Model Context Protocol server at https://sitegpt.ai/mcp. Any MCP-aware assistant, such as Claude, connects to it, asks you to approve access in the browser via OAuth, and can then create and manage SiteGPT chatbots on your behalf.
How do I connect Claude to SiteGPT?: Open Claude’s integrations or connectors settings, add a custom MCP server, and enter https://sitegpt.ai/mcp. Claude opens SiteGPT’s OAuth approval page; review the permissions and chatbot access, click Connect, and the SiteGPT tools appear in Claude.
Why does the server expose only two tools?: By design. Instead of one tool per endpoint, the server ships a compact pair: search finds the right SiteGPT API v2 operation from the catalog, and execute calls it. The assistant composes the whole platform from those two, and your context window is not flooded with a hundred tool definitions.
Do I paste an API token into the assistant?: No. The approval page creates an OAuth grant for the AI client. During approval SiteGPT shows the app requesting access, the permissions, and whether it can reach all chatbots or only selected ones. The grant never exceeds what your dashboard role allows, and you can revoke it.
Can I run the MCP server locally instead?: Yes. npx -y @sitegpt/cli mcp runs the same server over stdio for clients that launch local processes, such as Claude Code, Cursor, and Codex. Remote and local reach the same account.
Does it work without a SiteGPT account?: Chatbot management over MCP uses your account via OAuth. To try SiteGPT with no account at all, agent-first onboarding (documented at sitegpt.ai/auth.md) lets an agent build and train a chatbot from a URL and hand back a preview-and-claim link.

The same platform trusted with real support traffic

Hand your assistant the keys

One URL, one browser approval, and your AI assistant runs your support platform.

All agent surfaces →Explore the CLI →