MCP server
Connect Claude, Cursor, VS Code or any other MCP client to your website, and work on it from the AI assistant you already use.
Connect your own AI assistant, like Claude, Cursor or VS Code, to your website over MCP (the Model Context Protocol). Once it's connected, ask it to write pages and content, change the design, add libraries and animations, read your analytics to see what to improve, and build the site to check its work. It publishes only when you tell it to.
MCP is the best fit for larger and more complex changes. For everyday edits, the built-in AI Assistant is quicker. See Ways to build a site.
- Copy the site's MCP URL
- Your role applies (Admin or Editor)
- Setup for each client
- One-click setup
- Or a config snippet / command
Your site's MCP URL#
Each site has its own MCP URL, which always connects to that website. Copy it from the top of this screen. It looks like:
https://app.sleekcms.com/mcp/<site>
Working on several sites? Add each site's URL as a separate connection, and your assistant can work on all of them. Or use the general URL, https://app.sleekcms.com/mcp, and pick an existing site, or create a new one, when you sign in.
Connecting your assistant#
Pick your assistant below. In each, replace <your MCP URL> with your site's URL and <site> with your site's ID (the last part of the URL).
Claude (web and desktop)#
Click Add to Claude in the app: it opens Claude's Add custom connector dialog with the URL already filled in. To add it by hand, go to Settings → Connectors → Add custom connector in Claude, paste the URL, then click Connect to sign in.
Claude Code#
claude mcp add --transport http sleekcms-<site> <your MCP URL>
Then run /mcp in Claude Code, pick sleekcms-<site> and sign in.
Cursor#
Click Add to Cursor in the app, or add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project):
{
"mcpServers": {
"sleekcms-<site>": {
"url": "<your MCP URL>"
}
}
}
Cursor asks you to sign in the first time it connects.
VS Code#
Click Add to VS Code (or Insiders) in the app, or run:
code --add-mcp '{"name":"sleekcms-<site>","type":"http","url":"<your MCP URL>"}'
Use it from Copilot Chat in Agent mode. VS Code asks you to sign in when it starts the server.
Antigravity#
Open MCP Servers → Manage MCP Servers → View raw config, then add:
{
"mcpServers": {
"sleekcms-<site>": {
"serverUrl": "<your MCP URL>"
}
}
}
Other clients#
Any client that supports remote MCP servers over HTTP (Streamable HTTP) with OAuth sign-in can connect. Most use this shape (Windsurf calls the field serverUrl):
{
"mcpServers": {
"sleekcms-<site>": {
"url": "<your MCP URL>"
}
}
}
Signing in#
The first time your assistant connects, it opens a SleekSite sign-in page. Sign in and approve access to the site. From then on, the assistant acts as you, with your role on that site: a Site Admin's assistant can change everything (content, models, code, building and publishing), while an Editor's can only do what an Editor can. See Site members.
Sharing with teammates#
Everyone who works on the site can use the same MCP URL. Each person signs in with their own SleekSite account and gets their own role. People who aren't members of the site can't connect, so invite them first.
Testing with a token#
For developers using curl, the MCP Inspector, or a client that can't sign in through a browser: copy a bearer token for your account from this screen, and send it with each request:
Authorization: Bearer <token>
WarningTreat the token like a password. It gives full access as you on this site, and stays valid until you log out of all sessions.
Disconnecting#
Connections don't expire on their own.
- Remove one assistant: delete the connection in that assistant's settings
- Cut off every assistant at once: open your account menu, choose Logout and select All sessions. Each assistant has to sign in again before it can reconnect
For what an AI client can do and how to get the most from it, see MCP & AI clients. To load your content into your own app instead, see Headless CMS.