Run your site from Claude or Cursor: a CMS with an MCP server built in

Most of what people do in a CMS admin is small and repetitive. They write a meta description for each product that has none, redirect the pages that started returning 404, replace an old phone number on twelve pages, or check how many orders came in today. An AI agent is good at exactly that kind of work, as long as it can reach the site and you can trust what it reaches.

kitloom ships an MCP server for that. Turn it on and the site has an address, https://your-site/mcp. Claude Code, Cursor, Claude Desktop, claude.ai or any other MCP client connects to it with a key, and then runs the site from its chat.

Connecting takes a minute

1. In the admin, AI agents → Settings: turn agents on.
2. AI agents → Connect an agent makes a key and shows the settings ready to paste.
3. Paste them into the agent. For Claude Code that is one line:

claude mcp add --transport http kitloom https://your-site/mcp --header "Authorization: Bearer 12|…"

In claude.ai it's a custom connector with the same URL and header. That works on the web, on a phone and in Claude Desktop. Cursor takes the same two values in .cursor/mcp.json. The AI Agents guide has every client.

What the agent can do

Its first call is describe_site. It returns the post types and taxonomies, what each one supports, which fields show where, the menu places, and what the key's user may do with each type. Then it has tools for the whole site:

• Content. It can list, read, create and update posts, pages and any post type. It can move records to the trash and restore them, manage terms, upload media from a link or a file, and change settings.
• Seeing the site. resolve_url tells what lives at an address and which template draws it. render_page shows a page as a visitor sees it, as text, HTML or the page's parts as JSON, including a draft's preview.
• The modules' tools. Every installed module adds its own: SEO meta, redirects and the 404 log, menus, widgets, custom fields, forms and their messages, comments, the shop's products, orders, sales and coupons, bookings, courses, listings, translations, broken links, backups, the activity log, Site Health, webhooks and maintenance mode.

So you can ask for whole jobs, not single edits:

• "Fill in the SEO descriptions of the products that have none."
• "Which addresses gave 404 this week? Redirect the ones that have a new page."
• "Find the pages that still mention the old phone number and fix them."
• "Write a draft post about our spring collection, put it in News, and take the cover from this link."
• "How did the shop do this month, and which products sold best?"

The video lessons show a real agent doing these on a demo site. The chat is on the left, and every tool call changes the site on the right.

Exactly the access you give it

Handing an agent the keys to a production site is the part that worries people, and it's the part kitloom was designed around:

• The agent works as a user. The key is that user's application password. The agent sees and writes what that user may, through the same code the admin uses. An author's key writes drafts, an editor's publishes, and a read-only key gets only the reading tools.
• Nothing is deleted for good. Records go to the trash and can be restored. Permanent deletion stays with a person in the admin.
• Some settings are out of reach. Secrets and the site address are never shown. Settings that decide who gets in (registration, roles, two-factor), the doors into the site (agents, the REST API) and the code on every page (header scripts, tag manager, analytics) are locked. The agent sees them but can't change them, because a page it reads could try to talk it into it.
• Everything is written down. The activity log records each change under the key's user. Revoking the key stops the agent at once.
• Requests are limited. Each user gets 120 requests a minute by default.

When the site should ask a model itself

An agent is your subscription working on the site from outside. Sometimes you want the opposite: a Translate with AI button for an editor who has no AI account. AI Writer does that. You save a provider key on the site once with a monthly budget, the modules that write text get "with AI" buttons, and every question is logged with its cost. Two Ways to Use AI compares the two.

Try it

Every demo sandbox comes with a key ready on the dashboard, so you can connect your own Claude or Cursor to a site of your own in a couple of minutes, with no sign-up: Filament demo or Nova demo.

And if your site is on WordPress today, it can move to kitloom with its database as it is, and then an agent can run it.