Connect an AI assistant with MCP

​

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

https://sitegpt.ai/mcp

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

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

https://sitegpt.ai/mcp

​

Connect with read-only access

• Can list chatbots and read conversations, leads, escalations, analytics, knowledge sources, settings, and appearance. execute_read, open_sitegpt, and open_sitegpt_inbox work.
• Cannot create, change, or delete data. For example, execute_write, reply_to_conversation, send_chat_message, update_chatbot_appearance, update_sitegpt_settings, create_knowledge_source, authorize_knowledge_source, and upload_knowledge_file fail, and so do the reply form and the Connect and Upload and train forms of the Knowledge tab in the views. These calls return 403 TOKEN_SCOPE_NOT_ALLOWED. error.details.requiredScopes lists the permission that the call needs.

​

Connect the local server

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

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

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

​

Check that it works

List my SiteGPT 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. You can also limit the app to read-only access. See Connect with read-only access.
• In the list that starts with “This will allow”, the approval page sums up the permissions in groups: Chatbots, Knowledge, Customization, Conversations and leads, Team and account, Billing management, API tokens, and Integrations. A group shows only if the app gets a permission in it. If the app gets only read permissions in a group, the group says so, for example “View your chatbots and their details.” Advanced permissions lists each permission.
• 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.
• When you approve an app again, its other connections stay connected. For example, ChatGPT can hold more than one connection to SiteGPT. Each connection shows on the Agents page.
• You can revoke a connection at any time. See Manage connections.

​

HIPAA workspaces

• list_conversations, get_conversation, reply_to_conversation, list_escalations, and list_leads return 403 HIPAA_AI_ASSISTANTS_DISABLED. So do execute_read and execute_write calls to the conversation and lead endpoints.
• send_chat_message can start a new conversation, but it cannot continue one.
• In the open_sitegpt home view, the Inbox, Escalations, and Leads tabs show the refusal message. Analytics and Knowledge work.
• If SiteGPT cannot check the HIPAA status, these calls return 503 HIPAA_CHECK_UNAVAILABLE. Try again in a moment.
• This block does not affect the other tools, for example settings, analytics, appearance, and preview. Other HIPAA limits still apply, for example the limits on cloud file connectors. See Content.

​

Manage connections

​

Tools

​

Remote server tools

​

Local server tools

​

Troubleshooting

​

Documentation MCP server