Skip to main content

Connect other MCP tools

The SitePack connector is a standard MCP server, so it is not limited to one AI tool. Any assistant or client that supports the Model Context Protocol can connect to your site and use the same tools, with the same rules: one site per connection, only the permissions you approve, revocable at any time.

The connector address is your admin address followed by /api/mcp, for most customers:

https://admin.sitepack.eu/api/mcp

How a tool authenticates​

There are two ways, and which one you use depends on the tool:

  • Browser sign-in (OAuth). Tools that support OAuth for MCP open the SitePack sign-in and consent screen for you. Tools that only speak the local (stdio) protocol can use the mcp-remote bridge to get the same browser sign-in, see the Codex CLI page for a concrete example.
  • A personal access token. Ask your SitePack contact for a token tied to your site, and set it as an Authorization: Bearer header in the tool's MCP configuration. Keep it private, and have it revoked if it ever leaks.

What every connection can do​

The same tools regardless of the client: pages, menus, media, products, categories, tags and translations, on the one site the connection is bound to. See Connect Claude for the full list.

Same guarantees everywhere

No matter which tool connects, the connector never requests anything that spends money, and it can only touch the single site it was granted. Remove it in the tool's settings, or ask for the token to be revoked, to stop the connection.