Connect an AI assistant with MCP

The SiteGPT MCP server lets an AI assistant work on your SiteGPT account. The assistant can list chatbots, read conversations and leads, add content, and change settings. It uses the Model Context Protocol (MCP). There are two ways to run it:

Server	Address	Sign-in	Best for
Remote server	`https://sitegpt.ai/mcp`	You approve access in the browser (OAuth). Nothing to install.	Claude, ChatGPT, Cursor, and other apps that support remote MCP servers
Local server	`npx -y @sitegpt/cli mcp`	A CLI login or an API token	Apps that start local (stdio) MCP servers

Both servers act on your SiteGPT account. Neither can do more than your dashboard role allows. They have different tools. See Tools.

Before you start

A SiteGPT account on the Growth plan or above. See Plans and limits. On a lower plan, the approval page shows “API access needs the Growth plan or above.” instead of the permissions. Calls fail with 403 PLAN_UPGRADE_REQUIRED.
The assistant can do only what your dashboard role allows.
For the local server: Node.js 18 or later.

Connect the remote server

Claude (web and desktop)
ChatGPT
Claude Code
Cursor
Other apps

Open the connector settings

In Claude, open Settings > Connectors.

Add SiteGPT

Find SiteGPT in the connectors directory and select Connect. Or add a custom connector with this URL:

https://sitegpt.ai/mcp

Approve access

SiteGPT opens an approval page. Review the permissions and the chatbot access, then select Connect.

Run this command in your terminal:

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

Claude Code opens the SiteGPT approval page in your browser. Select Connect.

Add the server to .cursor/mcp.json:

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

Cursor opens the SiteGPT approval page in your browser. Select Connect.

Add a remote MCP server with this URL:

https://sitegpt.ai/mcp

The app must support remote MCP servers over Streamable HTTP with OAuth. When it connects, SiteGPT asks you to approve access in the browser.

Connect the local server

The local server runs on your computer through the SiteGPT CLI. It uses your CLI login or an API token.

Run sitegpt login, or set the SITEGPT_API_TOKEN environment variable to an API token. See Install and log in and Authentication.

Add the server to your app

Claude Code
Cursor
Codex
Other apps

claude mcp add sitegpt -- npx -y @sitegpt/cli mcp

.cursor/mcp.json

{
  "mcpServers": {
    "sitegpt": {
      "command": "npx",
      "args": ["-y", "@sitegpt/cli", "mcp"]
    }
  }
}

~/.codex/config.toml

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

Use npx as the command and -y @sitegpt/cli mcp as the arguments. If the CLI is installed, you can also run sitegpt mcp.

The npm package @sitegpt/mcp also starts the local server. It runs npx -y @sitegpt/cli mcp for you.

Check that it works

Ask the assistant:

List my SiteGPT chatbots.

The assistant calls a SiteGPT tool and shows your chatbots.

Permissions

The assistant can never do more than your dashboard role allows.
On the approval page, you can see the permissions and chatbot access. Permissions that your role does not allow are left out.
The remote server also accepts an API token (sgpt_...) as a bearer token, for apps that cannot do OAuth.
A connected app renews its access in the background. You do not need to approve it again each time.
You can revoke a connection at any time. See Manage connections.

Manage connections

Open Agents in the top navigation. The MCP connections section lists each app that you approved. Select Revoke to disconnect an app. The local server uses an API token instead. Manage it in the token list on the same page.

Tools

Remote server tools

The remote server has 3 tools that reach all of API v2, plus tools for common jobs.

Tool	What it does
`search`	Finds the right API v2 operation.
`execute_read`	Runs read-only API v2 calls (`GET`).
`execute_write`	Runs API v2 calls that create, change, or delete data.
`preview_chatbot`	Shows a live preview of a chatbot.
`send_chat_message`	Sends a visitor message to a chatbot and returns the answer.
`get_onboarding_status`	Shows the setup status of an onboarding chatbot.
`get_chatbot_appearance`, `update_chatbot_appearance`	Reads or changes the widget appearance.
`list_conversations`, `get_conversation`	Lists conversations and reads one conversation.
`get_chatbot_analytics`	Reads chatbot analytics.
`list_leads`	Lists leads.
`list_escalations`	Lists escalated conversations that wait for your team.
`list_knowledge_sources`, `create_knowledge_source`, `authorize_knowledge_source`	Lists connected sources, connects a new source, and gets a new authorization link.
`upload_knowledge_file`	Uploads one file as content.

Apps that support MCP app views can show some of these results as interactive views in the chat. execute_write cannot create or change GitHub sources, because they carry an access token. Connect GitHub in the dashboard. See Connect GitHub.

Local server tools

The local server has its own tools, named sitegpt_..., for example sitegpt_whoami, sitegpt_list_chatbots, and sitegpt_send_message. They match the CLI commands. See Command reference.

Troubleshooting

The approval page does not return to the app

Check that a pop-up blocker or privacy extension does not block the page.
Make sure you are signed in to the right SiteGPT account in the same browser.
Remove the server in the app and add it again.

The app shows no SiteGPT tools

The remote server needs sign-in before it shows any tools. Finish the approval in the browser. If the app does not open the approval page, check that it supports remote MCP servers with OAuth.

A SiteGPT call fails

Ask the assistant for the status code and error code. Common causes are a permission your role does not have, a chatbot the connection cannot access, or a revoked connection. See API conventions.

The CLI works but the remote server does not

The CLI and the remote server sign in in different ways. Remove the server in the app and connect it again.

Documentation MCP server

These docs have their own MCP server at https://sitegpt.ai/docs/mcp. It needs no sign-in. It lets an assistant search and read the SiteGPT documentation. It cannot access your account.

Get started

Concepts

Add content

Improve answers

Customize the widget

Install

Leads

Human support

Monitor

Integrations

Account and team

Reference

Developers

Help

Connect an AI assistant with MCP

Before you start

Connect the remote server

Connect the local server

Check that it works

Permissions

Manage connections

Tools

Remote server tools

Local server tools

Troubleshooting

Documentation MCP server

​Before you start

​Connect the remote server

​Connect the local server

​Check that it works

​Permissions

​Manage connections

​Tools

​Remote server tools

​Local server tools

​Troubleshooting

​Documentation MCP server

Before you start

Connect the remote server

Connect the local server

Check that it works

Permissions

Manage connections

Tools

Remote server tools

Local server tools

Troubleshooting

Documentation MCP server