Fill a site with content through an agentCopy Anchor Link

An agent connected over MCP can find, write and publish your pages, blog posts and services, add and arrange the sections of a page, bring in images, preview the result and undo its own changes. It works with your account, on the projects you can reach.

ConnectCopy Anchor Link

The MCP address of BOLDCMS is:

https://cms-production.boldcms.dev/api/mcp/v2

In Claude Code, add it once:

claude mcp add --transport http boldcms https://cms-production.boldcms.dev/api/mcp/v2

Then run /mcp inside a Claude Code session. A browser window opens:

1. Sign in with the account you use for the admin.
2. On the consent screen, check what the agent asks for and choose Authorise.

The agent is connected. Other MCP clients that register themselves, such as Cursor, connect the same way: give them the address and sign in when the browser opens.

The claude.ai web connector does not register itself. It asks for an OAuth client ID and secret issued for it, which this page does not cover yet.

Stay connectedCopy Anchor Link

The consent screen ends with Stay connected. Approve it and the connection renews itself for 30 days from its last use. Without it, the agent asks you to sign in again every hour. Signing out of the admin does not disconnect an agent that stays connected.

A smaller or a full set of toolsCopy Anchor Link

The address above offers the agent a working set for daily content work: pages, blog posts, services, images, page SEO, preview and undo. To offer it everything your permissions allow, including the site header and footer, the logo, contact details and navigation, connect to /api/mcp/v2/full instead:

https://cms-production.boldcms.dev/api/mcp/v2/full

AskCopy Anchor Link

Start by asking where the agent is:

Which BOLDCMS projects can you reach, and in which languages?

It lists the projects your account may manage, with their content languages. Then name the project and ask for the work:

In the project <your-project>, write a blog post about our new opening hours. Keep it as a draft and show me a preview.

On the About page, add a call to action at the end, linking to Contact. Show me the preview before you publish.

Run a content health check and fix the missing meta descriptions it finds, in English.

What the agent can doCopy Anchor Link

• Find, create, update and publish pages, blog posts and services.
• Add a section to a page, edit it, move it or remove it.
• Find images in the media library, and upload a new one from a public https address (up to 5 MB) or from a small file of about 1.5 MB. PNG, JPEG, GIF, WebP, AVIF and SVG are accepted. It can also fill in an image's alt text.
• Set the SEO of one page, blog post or service: title, description, share image, focus keyword, canonical address, robots and whether it is left out of the sitemap. Like any other edit, it goes to the draft until published.
• Run a content health check, which reports problems such as missing alt text or a meta description of the wrong length.
• Preview a page: it gets the page's address and, when one can be taken, a screenshot.
• Show a page's saved versions and restore an earlier one. See Undo a change an agent made.
• List what agents changed in a project, newest first.

The rules it works underCopy Anchor Link

Writes go to the draft. Pages, blog posts, services, portfolio items, events and forms keep a draft. Everything the agent writes to them lands in the draft, and a page that is already live keeps showing the published version. Visitors see a change only when it is published. Setting the status in an ordinary edit does not publish: the edit is kept as a draft.

Some things have no draft. The site header and footer, the logo, company and contact details, social links, SEO defaults, and entries such as team members, addresses, logos and stats are live the moment the agent writes them. There is no publish step and no draft to fall back on. These tools are on the full set only.

One language at a time. Text is stored per language. Writing one language leaves the others as they were, so ask for each language you want changed.

It previews before it acts. Publishing, removing a section, setting SEO and restoring a version first answer with what would happen, and change nothing until the agent confirms. The agent gives that confirmation itself. If you want to approve first, say so in your request: "show me what would change, then wait".

It writes with an editor's rights. Whatever your own role, the agent edits as an editor. A change that needs more is refused, and the answer names the role that would be needed.

What it cannot doCopy Anchor Link

• Set a blog post's author.
• Publish by any route other than the publish step.
• Restore a version as the live page: a restore always lands on the draft.
• Go further back than the 10 newest versions of a document.
• Upload an image from an address that is not public https, or one larger than 5 MB.
• See changes made in the admin in its list of changes: that list holds only what agents changed.