How do I add SiteGPT to Cursor?

Add a sitegpt entry to your .cursor/mcp.json with the remote server URL https://sitegpt.ai/mcp (OAuth approval opens in the browser), or point it at npx -y @sitegpt/cli mcp to run locally. Then enable it in Cursor settings.

Do I need an API key to start?

No. Cursor can build and train a chatbot from a URL with no SiteGPT account through agent-first onboarding, and hand back a claim link.

Should the server go in the project config or the global one?

Project (.cursor/mcp.json, committed) when the connection belongs to the codebase: the client site whose support bot this is, inherited by everyone who clones. Global (~/.cursor/mcp.json) when it belongs to you: one SiteGPT account you use across every project. Agencies typically do both: global for their own account, project files scoped to each client.

Can Cursor manage existing chatbots too?

Yes. Once authenticated, Cursor can manage knowledge, settings, conversations, and leads across all your chatbots.

Cursor is not picking up the MCP server. What do I check?

Validate the JSON first (trailing commas are the classic), confirm the file is .cursor/mcp.json at the project root or ~/.cursor/mcp.json globally, check the server is enabled in Cursor’s MCP settings, and restart the session. Remote entries need url; local entries need command and args; a mixed entry fails silently.

SiteGPT × Cursor

Ship a support agent from Cursor

Give Cursor the SiteGPT MCP server and your agent can create, train, and manage support chatbots without leaving the editor.

All agent surfaces →

cursor agent

> Set up SiteGPT support for docs.acme.com   created + trained chatbot  enabled lead form and human handoff  embedded the widget snippet  ✓ done, preview and claim link ready

Connect in two minutes

Connect SiteGPT to Cursor

Point Cursor at the remote SiteGPT MCP server (OAuth approval opens in your browser), or run the server locally over stdio. Then ask Cursor to build a chatbot for your site.

.cursor/mcp.json

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

Cursor is the AI code editor. Learn more at Cursor.

MCP in Cursor

How .cursor/mcp.json works

Cursor loads MCP servers from .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally. Remote servers take a url; local ones take a command and args. Cursor picks the file up automatically, and the tools appear to its agent, which asks before running anything marked destructive.

Project-level config is the quiet superpower: commit .cursor/mcp.json and every teammate who clones the repo gets the same tool set. SiteGPT works at either level from the same account, and authenticates with browser OAuth, so no key ever sits in the JSON.

The practical division of labor: your code-facing servers help Cursor build the product, and SiteGPT gives it the customer-facing lane, so the same agent that shipped the feature can ship the support for it.

When tools do not appear, the checklist is short: confirm .cursor/mcp.json parses (a trailing comma is the classic), check the server toggle in Cursor settings under MCP, and restart the session so the config reloads. Remote entries need the url key, local ones command plus args; mixing the two shapes silently fails.

Zero to operated

Ship the support with the feature

Cursor already ships your product. With SiteGPT in .cursor/mcp.json, it ships the support for it too, in the same session.

Add the server to the project

Drop the mcpServers entry into .cursor/mcp.json and commit it: every teammate who clones the repo gets the connection. Auth is browser OAuth on first use; the JSON never holds a key.

Ship the bot with the site

While Cursor builds the marketing site, ask it to create the support chatbot from the same sitemap, then paste the embed snippet into the layout it just wrote.

Debug with real conversations

Fixing checkout? Pull the five most recent support conversations that mention it. The bug report and the reproduction steps are usually already in there, written by your users.

Close the loop before you merge

Docs updated in the branch get re-queued for training, so the answer your support bot gives about the feature matches the code that ships it.

Input → outcome

Your agent types the left side.
Your customers see the right.

agent session

> Stand up support for acme.com   created chatbot (no account)  trained 142 pages + help center  set persona + brand colors  ✓ live, claim link ready

🤖

Acme Support

Online · answers instantly

Do you ship to Canada?

Yes! We ship to Canada on all plans. Standard delivery takes 5-7 business days and duties are included at checkout.

Source: acme.com/shipping

Anything else I can help with?

Ask anything…

Works in any agent that can read a URL: it discovers the no-signup onboarding flow on its own.

Why SiteGPT for Cursor

Never leave the editor

The docs site you are editing and the chatbot that answers from it live in the same Cursor session: change the docs, retrain the bot, embed the widget, all from agent mode.

Per-project by design

The server rides in .cursor/mcp.json, so each project can carry its own SiteGPT connection: your product in one repo, a client site in another, each scoped to its own chatbots.

No signup to start

Cursor can spin up a real, trained chatbot from a URL with no SiteGPT account. You only sign up to keep it.

Steal these

Prompts for the next session

Everything below runs against your live account once connected. Reads run freely; anything that changes data asks first.

“Set up a support chatbot for this project’s marketing site.”

Created and trained from the sitemap, embed snippet ready to paste.

“Pull the five most recent support conversations mentioning the checkout flow.”

Live transcripts, useful context while you fix the bug they describe.

“Update the bot’s instructions to mention the new onboarding flow.”

A reviewed write: Cursor shows the change, you approve, it lands.

“List the leads the support bot captured this week with their questions.”

Fresh leads with context, ready to hand to whoever follows up.

Cursor + SiteGPT, answered

How do I add SiteGPT to Cursor?: Add a sitegpt entry to your .cursor/mcp.json with the remote server URL https://sitegpt.ai/mcp (OAuth approval opens in the browser), or point it at npx -y @sitegpt/cli mcp to run locally. Then enable it in Cursor settings.
Do I need an API key to start?: No. Cursor can build and train a chatbot from a URL with no SiteGPT account through agent-first onboarding, and hand back a claim link.
Should the server go in the project config or the global one?: Project (.cursor/mcp.json, committed) when the connection belongs to the codebase: the client site whose support bot this is, inherited by everyone who clones. Global (~/.cursor/mcp.json) when it belongs to you: one SiteGPT account you use across every project. Agencies typically do both: global for their own account, project files scoped to each client.
Can Cursor manage existing chatbots too?: Yes. Once authenticated, Cursor can manage knowledge, settings, conversations, and leads across all your chatbots.
Cursor is not picking up the MCP server. What do I check?: Validate the JSON first (trailing commas are the classic), confirm the file is .cursor/mcp.json at the project root or ~/.cursor/mcp.json globally, check the server is enabled in Cursor’s MCP settings, and restart the session. Remote entries need url; local entries need command and args; a mixed entry fails silently.

The same platform trusted with real support traffic