AI Agents
Pro plan. Available on Pro and above, during the free trial, and in every self-hosted install.
AI agents can read and edit your sites through the Sitepins MCP server. You decide which sites each agent reaches and what it may change, and every change it makes is committed by the Sitepins bot, never with your personal Git account.
Connect an agent
- Open Settings → MCP Connection and click Create token.
- Name the token after the agent (for example, Claude Desktop), pick the organization, sites, permissions and how changes are saved. Choose All sites to include every site in the organization, including ones added later, or pick specific sites.
- Click Copy prompt and paste it into your agent.
The prompt tells the agent how to add Sitepins to its own MCP settings, whatever app it runs in: Claude Code, Claude Desktop, Codex, Cursor, VS Code, Antigravity, Windsurf, Gemini CLI or any other MCP client. If the agent can’t edit its settings itself, it tells you which file to open and what to paste.
The token is shown only once. If you lose it, revoke it and create a new one.
Manual setup
Every client uses the same two values, also shown under Manual setup:
- Server URL:
https://<your API>/mcp(Streamable HTTP) - Header:
Authorization: Bearer <your token>
For example, in Claude Code:
claude mcp add --transport http sitepins https://api.sitepins.com/mcp --header "Authorization: Bearer spat_..."Just ask in plain words
You don’t need to know file names or Git. Ask the agent the way you’d ask a colleague:
- “Change the homepage banner to red.”
- “Fix the typo in the About page title.”
- “Add Jane to our team as an editor.”
- “Can I add another site on my plan?”
The agent finds the right file, makes the change and tells you what it did. Every change is saved as soon as it’s made, so “save”, “push” or “publish” needs no extra step. If the token is set to save through pull requests, the change waits for someone to merge it, and the agent gives you the link. Ask “is it live?” and the agent checks what your hosting provider reports: live, still building, or failed with the reason. To undo, say “undo that”: the agent puts back the earlier version as a new change. It won’t overwrite anything someone edited since.
If a change needs a permission the token doesn’t have, for example colours and layouts usually need Edit code, the agent tells you which setting to turn on in Settings → MCP Connection.
Permissions
| Permission | Lets the agent |
|---|---|
| See sites, Read files | Find and read anything in the sites you picked (always on) |
| Edit content | Change content and settings files |
| Manage media | Upload, rename and delete media |
| Edit schemas | Change content schemas and snippets |
| Edit code | Change templates, styles and other site code (off by default) |
| Branches and pull requests | Save to other branches and open pull requests |
| See organization | Read the organization’s members and roles, and on Sitepins Cloud your plan, usage and billing history (off by default) |
| Manage members | Invite members, change their roles and remove them; never the owner (off by default) |
What the agent can do
| Tool | What it does |
|---|---|
list_projects | Sites the token can access |
get_project_context | A short map of the site: content and media folders, schema names, where settings, styles and templates live, and what the token may change |
search_content | Finds text in the site, content first and then templates and styles |
list_files, read_file, read_files, get_schema, list_history | Browse the repository, including older versions |
edit_file | Replace text inside a file without sending the whole file |
write_files | Create, edit and delete files in one commit |
move_file | Rename or move a file |
undo_change | Undo an earlier change by putting back the files it touched |
get_deploy_status | Whether a change is live, still building, or failed, as your host reports it |
get_clone_command | For agents that can run a terminal: commands to clone the site or bring a local copy up to date (“sync”), and whether it needs one. They carry a one-hour, read-only key, so nothing is stored and git never asks for a password |
get_organization, invite_member, update_member_role, remove_member | See and manage the organization’s members |
get_plan_usage, get_billing_history, check_limit | Sitepins Cloud: your plan, limits and usage, past orders, and whether an action fits your plan. The agent can read these but never change your plan; that stays on the billing page. |
Agents that clone the site still save through write_files; git push is refused. If someone changed the same file in the meantime (in the editor, or another agent), Sitepins returns the current version instead of committing, so nobody’s work is overwritten.
What you’ll see
- Commits come from the Sitepins bot (
sitepins[bot]on GitHub,Sitepinson GitLab) and name you and the agent in the message. - Activity on the project page shows each change with the agent’s name.
- Open editors get a notice when an agent changes a file someone is editing. Publishing then shows what changed first.
Revoking access
Settings → MCP Connection lists every token with when it was last used. Revoke cuts the agent off on its next request. Tokens also expire after 7, 30 or 90 days, and removing someone from an organization disconnects their tokens for it.