Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Manage SiteGPT chatbots and account resources through the SiteGPT API v2.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://sitegpt.ai/mcpRun this in your terminal
claude mcp add --transport http sitegpt https://sitegpt.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sitegpt": {
"url": "https://sitegpt.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sitegpt": {
"type": "http",
"url": "https://sitegpt.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://sitegpt.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account sitegpt, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Whisper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Official SiteGPT skills for AI agents.
These skills teach agents how to use SiteGPT through the SiteGPT CLI so they can manage chatbots, knowledge, conversations, settings, team access, and account resources from an agent environment.
SiteGPT also publishes https://sitegpt.ai/auth.md for agent environments that support Auth.md-style discovery of the anonymous try-before-signup onboarding flow.
As a Claude Code plugin (also works in Cowork):
/plugin marketplace add sitegpt/agent-skills
/plugin install sitegpt@sitegpt
With the skills CLI (any agent environment that supports Agent Skills):
npx skills add sitegpt/agent-skills
Both deliver the same skill. This repository is dual-packaged: an Agent Skills repo (skills.sh) and a Claude Code plugin marketplace (.claude-plugin/).
Orientation skill: what SiteGPT is, which surface to use (CLI, MCP connector, REST API, or no-signup onboarding), and where the deep workflows live. Routes terminal work to sitegpt-cli.
Use the SiteGPT CLI to manage SiteGPT accounts and chatbots from AI agents such as Codex, Claude Code, Cursor, OpenCode, Gemini CLI, Windsurf, Cline, and other skill-compatible coding agents.
Use when:
The skill is a single self-contained SKILL.md: the agent-facing workflow, discovery brief, onboarding and account playbooks, command map, and safety rules in one file. The SiteGPT CLI itself is the source of truth for exact command syntax — agents run sitegpt --help for flags, so the skill deliberately does not duplicate a per-command reference.
This repository is also a Cursor plugin (skills + the remote MCP server). In Cursor, run /add-plugin and pick SiteGPT, or install from the marketplace listing. The MCP server connects your SiteGPT account with browser OAuth; the skills work with no account via agent-first onboarding.
Install the SiteGPT CLI skill with the open skills CLI:
npx skills add sitegpt/agent-skills --skill sitegpt-cli
Install into a specific agent:
npx skills add sitegpt/agent-skills --skill sitegpt-cli -a codex
npx skills add sitegpt/agent-skills --skill sitegpt-cli -a claude-code npx skills add sitegpt/agent-skills --skill sitegpt-cli -a cursor
Install globally:
npx skills add sitegpt/agent-skills --skill sitegpt-cli --global
List available skills without installing:
npx skills add sitegpt/agent-skills --list
Update installed skills later:
npx skills update sitegpt-cli
The skills CLI installs this agent skill. The SiteGPT CLI is the actual command-line tool the agent will run after the skill is installed.
Install the SiteGPT CLI first:
npm install -g @sitegpt/cli
Then choose the right flow:
sitegpt onboarding start , configure and test the temporary chatbot, then share the onboarding URL for preview and claim.For existing accounts, authenticate with device login:
sitegpt login
You can also create an API token from the SiteGPT dashboard and save it manually:
sitegpt login --token <sitegpt-api-token>
Once the skill is installed, ask your agent:
Try SiteGPT for https://example.com. Inspect the website, create a temporary chatbot, add knowledge, configure persona and instructions, test it, and give me the onboarding URL so I can preview and claim it.
I already have a SiteGPT account. Create a chatbot for https://example.com inside my account, configure knowledge and branding, and give me the dashboard link.
Audit my SiteGPT chatbot knowledge sources and resync any failed or stale documents.
Show recent conversations for my SiteGPT chatbot, summarize unresolved issues, and tag the conversations that need human follow-up.
skills/
sitegpt-cli/ SKILL.md
Skill versions live in metadata.version inside each SKILL.md and in the root package.json.
Releases are manual. When publishing a new version:
package.json.metadata.version in each changed SKILL.md.CHANGELOG.md.chore: release .v0.1.2.Users who install through npx skills add sitegpt/agent-skills can update later with npx skills update.
MIT