Connect Cursor
The Cursor editor can work on your SitePack site through the connector. It uses the Model Context Protocol (MCP), so once it is connected you can ask Cursor's agent to read or change your site's content, on the one site you approve.
This page assumes you use the Cursor editor. If you just want an AI assistant on your site without an editor, the Claude desktop app is the simplest option.
Connect with browser sign-in
Add the connector to Cursor's MCP configuration. Use ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside a single project:
{
"mcpServers": {
"sitepack": {
"url": "https://admin.sitepack.eu/api/mcp"
}
}
}
Then open Cursor Settings → MCP (Tools & Integrations). SitePack appears in the list with a login button because it needs sign-in. Click it: Cursor opens the SitePack sign-in and the permission screen in your browser, where you choose your site and press Approve. Cursor remembers the sign-in afterwards.
Once the server shows as connected, its tools are available to Cursor's agent.
In the agent, ask: "Using the SitePack tools, list the pages that have no meta description." Cursor will call the connector and show what it found.
What you can do
The same tools as every SitePack connection: pages, menus, media, products, categories, tags and translations, on the one site the connection is bound to. See Connect Claude for the full list, and the overview for exactly what you approve.
Frequently asked questions
The server shows as needing login
That is expected the first time, and again if the sign-in expires. Open Cursor Settings → MCP and use the login button to sign in again. See Troubleshooting for more.
Does Cursor get access to my whole account?
No. Like every SitePack connection, it is bound to one site and to the permissions you approve, and it never requests anything that spends money.
How do I disconnect?
Remove the sitepack entry from your mcp.json, or disable the server in Cursor Settings → MCP.