AI & Machine Learning
sitegpt.ai
SiteGPT deploys an AI chatbot trained on your website content to provide instant customer support.
ENDPOINT 1
https://sitegpt.ai/mcp
MCP server metadata
- Name
- sitegpt
- Version
- 1.0.0
SiteGPT chatbot management. Call search first to find the right API v2 endpoints, execute_read for GET lookups, execute_write to create or change resources. Purpose-built tools (preview_chatbot, list_conversations, get_chatbot_analytics, list_leads, list_escalations, list_knowledge_sources, get_onboarding_status, …) return compact data and render as inline app views on hosts that support MCP Apps. Authorization uses OAuth; server/discover, initialize, and tools/list work without it.
Known tools 17
execute_writeCreate, update or delete SiteGPT API v2 resources (POST, PUT, PATCH or DELETE only) using JavaScript code.
Potential side effectspreview_chatbotRender a live, interactive preview of a SiteGPT chatbot directly in the conversation (MCP Apps extension).
Inferred read-onlysend_chat_messageSend a visitor message to a SiteGPT chatbot and get its answer — the data lane behind the inline chatbot preview's built-in chat.
Potential side effectsget_onboarding_statusGet the live status of an agent-first onboarding workspace: workspace and claim state, the setup checklist (knowledge crawl/training, persona, starters, …), the browser onboarding page URL, and the POST-only claim API endpoint (claimUrl is for agents/CLI clients — never a page to open in a browser).
Potential side effectsget_chatbot_appearanceRead the chatbot widget appearance (colors, launcher position and shape, title, welcome message, placeholder, tooltip) plus its starter questions, for the inline appearance card.
Potential side effectsupdate_chatbot_appearanceUpdate the chatbot widget appearance: title, welcome message, placeholder, tooltip, brand/launcher/link colors (#rrggbb), and launcher position.
Potential side effectslist_conversationsList a chatbot conversation inbox with filters (open/resolved status, escalated-only) and cursor pagination, projected to compact rows with a last-message snippet.
Potential side effectsget_conversationRead one conversation with its transcript (visitor questions and chatbot/system answers, capped at 2000 characters per message).
Potential side effectsget_chatbot_analyticsGet chatbot analytics for the inline analytics card: message counts and feedback split, training/knowledge state (from the chatbot dashboard endpoint) plus account-wide quota usage and a 12-month message-volume history (from the usage endpoint).
Potential side effectslist_leadsList the leads a chatbot collected (name, email, phone, received time, starred/archived flags) with search, status filter, and cursor pagination.
Potential side effectslist_escalationsList the open conversations that are escalated to a human and waiting — the queue behind the inline escalations view — with cursor pagination for queues longer than one page.
Inferred read-onlylist_knowledge_sourcesList a chatbot connector data sources (Notion, Google Drive, Confluence, …) with their sync state, plus document counts by ingestion status.
Inferred read-onlycreate_knowledge_sourceCreate a new OAuth knowledge source connection (Notion, Google Drive, Dropbox, OneDrive, Box, SharePoint, or Confluence) and get the browser authorization URL to finish connecting it.
Potential side effectsauthorize_knowledge_sourceGet a fresh browser authorization URL for an existing knowledge source connection (for example one still pending OAuth).
Inferred read-onlyupload_knowledge_fileUpload one file (base64-encoded, max 1500000 bytes decoded — about 1.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sitegpt]
url = "https://sitegpt.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sitegpt": {
"type": "http",
"url": "https://sitegpt.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sitegpt
Remote MCP URL: https://sitegpt.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sitegpt": {
"url": "https://sitegpt.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sitegpt": {
"type": "http",
"url": "https://sitegpt.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sitegpt",
"transport": "streamable-http",
"url": "https://sitegpt.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://sitegpt.ai/docs/mcp
MCP server metadata
- Name
- SiteGPT Docs
- Version
- 1.0.0
This Model Context Protocol server provides search and retrieval tools for the SiteGPT Docs site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect, outdated, confusing, or incomplete — use the submit_feedback tool to report it to the docs team. Apart from the submit_feedback tool, the server is read-only and scoped to SiteGPT Docs; it does not otherwise perform actions, mutate state, or access anything beyond the published site content and these resources.
Known tools 3
search_site_gpt_docsSearch across the SiteGPT Docs knowledge base to find relevant information, code examples, API references, and guides.
Inferred read-onlyquery_docs_filesystem_site_gpt_docsRun a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the SiteGPT Docs documentation pages and OpenAPI specs.
Potential side effectssubmit_feedbackReport a problem with this documentation site so the docs team can fix it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sitegpt-docs]
url = "https://sitegpt.ai/docs/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sitegpt-docs": {
"type": "http",
"url": "https://sitegpt.ai/docs/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sitegpt-docs
Remote MCP URL: https://sitegpt.ai/docs/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sitegpt-docs": {
"url": "https://sitegpt.ai/docs/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sitegpt-docs": {
"type": "http",
"url": "https://sitegpt.ai/docs/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sitegpt-docs",
"transport": "streamable-http",
"url": "https://sitegpt.ai/docs/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.