Connect your AI agent
to BCMS content
Install the bcms skill, add BCMS as an MCP server, and manage entries and media in plain English. Works with Cursor, Claude Code, and OpenClaw.
npx skills add bcms/ai --skill bcms14-day free trial · No credit card required
Free · Open source · Available on skills.sh and ClawHub
Built for the agents you already use
Native MCP, agent skills, and scoped keys. Cursor, Claude Code, Codex, and more can create and update BCMS content without custom integration code.
AI agents
Connect BCMS over MCP. Agents create and update content from the tools you already use. Scoped keys control what they can access.
Connect Claude Code
Add this to .mcp.json
.mcp.json
claude mcp add --scope project --transport http bcms "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY_HERE"
Skill, MCP, and CLI do different jobs
The skill teaches your agent BCMS. MCP gives it live tools. The CLI gives scripts deterministic commands. Most teams use the skill and MCP together.
Knowledge
Agent Skill
Teaches your agent BCMS: concepts, content modeling, SDK usage with @thebcms/client, framework integrations, MCP tool usage, and security practices. Installed locally in Cursor, Claude Code, Codex, or OpenClaw.
Skill detailsLive tools
MCP
The live connection to your CMS. Templates, entries, groups, widgets, media, languages, statuses, entry history, and schema operations as MCP tools, scoped by key permissions.
MCP detailsDeterministic ops
Content CLI
Ships with the bcms-content skill. List, create, update, and delete entries and upload media from a terminal, with JSON output and stable exit codes for scripts and CI.
CLI commandsRecommended path
Follow these four steps to connect an agent safely and complete your first useful BCMS operation.
- 1
Install the bcms skill
Give your agent BCMS concepts, content-modeling guidance, SDK patterns, and MCP tool knowledge.
- 2
Create a scoped key in the BCMS dashboard
Create a dedicated key with access limited to the templates and media the agent needs.
- 3
Connect the MCP server in your client
Add the Streamable HTTP endpoint to Cursor, Claude Code, OpenClaw, or another supported client.
- 4
Ask the agent to inspect available templates
Verify the connection with a safe read operation before creating or updating content.
How it works
Three steps to go from install to your first BCMS entry.
- 1
Install the skills
Add bcms for MCP and SDK guidance. Add bcms-content if you want a terminal CLI for scripts and CI.
- 2
Connect your client
Create a scoped key in the dashboard, then paste the MCP config in Cursor or Claude Code, or set BCMS_API_KEY for the content CLI.
- 3
Manage content
Ask your agent to inspect templates, draft posts, upload media, or publish entries. Or run CLI commands that return JSON.
Agentic CMS
MCP, skills, and scoped access so AI agents can work with structured content safely.
Agentic workflows
From draft to publish, media to CLI. The content loop your agent can run end to end.
Works with your stack
Frameworks, starters, and search your team already expects from a headless CMS.
Teams building with BCMS
and of course, you
Get started
Install skills, connect MCP, or run the content CLI. Most teams start with bcms; add bcms-content for terminal workflows.
bcms v1.4.0
npx skills add bcms/ai --skill bcmsbcms-content v1.1.0
npx skills add bcms/ai --skill bcms-content- Works with Cursor, Claude Code, and Codex.
- Install bcms for SDK + MCP guidance; bcms-content for the executable content CLI.
- Repo: github.com/bcms/ai
Registries: skills.sh/bcms/ai/bcms · skills.sh/bcms/ai/bcms-content · Repo: github.com/bcms/ai
Security first
Agents get exactly the access you give the key, nothing more.
- Create separate credentials per person, per client, and per environment.
- Scope keys to the templates the agent needs (least privilege), including media-level permissions.
- Never put MCP keys or BCMS_API_KEY in frontend code, public repos, or shared screenshots.
- Rotate keys regularly and revoke any key immediately if it is exposed.
- Review entry history to audit what an agent changed.
- For destructive operations, list and confirm entry ids first and use scoped delete permissions.
Built for machines too
Every key page has a Markdown twin that agents can fetch directly.
- This page as Markdown
/agents.md - MCP reference
/mcp.md - Agent Skills reference
/agent-skills.md - Agent onboarding manifest
/llms.txt - Documentation index
/docs/llms.txt - Full documentation
/docs/llms-full.txt
Works with: Cursor, Claude Code, Codex, OpenClaw.
Try these prompts
Works after MCP and the bcms skill are connected. Copy a prompt and paste it into your agent.
Discoverylist-templates-and-entries
Show me all templates and entries I have access to in BCMS. Summarize by template name.Create contentcreate-entry-for-{templateId}
Create a new blog post in my Blog template titled "Getting Started with BCMS Agents". Write an introduction paragraph and set it to draft status for English.Update contentlist-entries-for-{templateId}
List all blog posts, find the "Getting Started" post, and expand the introduction with two more paragraphs.Delete contentdelete-entries
List blog entries, find the draft "Test post" by title, confirm the entry id with me, then delete it.Medialist-media-dirs
Show my media library folder structure, then create a folder called "Blog Images" if it doesn't exist.Upload workflowrequest-upload-media-url
I need to upload a hero image for a blog post. Get an upload URL, tell me how to upload it, then attach it to the post content.
FAQ
Common questions about BCMS MCP, agent skills, and content workflows.
How do I keep MCP keys safe?
Create a dedicated key per person, per client, and per environment with least-privilege template and media scopes. Never put MCP keys or BCMS_API_KEY in frontend code, public repos, or shared screenshots. Rotate keys immediately if they are exposed. Security & permissions
Do I need a BCMS account?
Yes. You need an active BCMS instance and an MCP key (or API key with the same three-part format) created in the dashboard under Settings - MCP or API keys.
Cursor vs Claude Code?
Same MCP URL and JSON config. Install bcms (and optionally bcms-content) in either client with npx skills add bcms/ai --skill bcms.
Skill vs MCP - do I need both?
The bcms skill teaches your agent BCMS patterns, SDK usage, and MCP tool names. MCP provides the live tools. We recommend using both together for agent workflows.
bcms vs bcms-content - which skill?
bcms covers SDK building, content modeling, framework integrations, and MCP reference. bcms-content is an executable CLI for create/update/delete/list entries and upload media - ideal for terminals, CI, and deterministic agent scripts. Use MCP for in-IDE agent tools; use bcms-content when you want a command that prints JSON.
Can my agent delete posts?
Yes. MCP exposes delete-entries when your key has delete permission for that template. The bcms-content CLI also supports delete-entry for scripted workflows, and requires confirmation (or an explicit --yes flag).
Can my agent change my content model?
Yes via MCP schema tools - templates, groups, widgets, statuses, and languages can be created and updated when your key has the right scopes. For day-to-day content work, agents usually operate on entries and media.
Can I use environment variables in Cursor mcp.json?
Unreliable. Cursor does not consistently expand env vars in MCP server URLs. Paste your key in local, user-level config only.
Custom BCMS host?
Replace app.thebcms.com in the MCP URL with your organization's dedicated BCMS app URL. For the content CLI, set BCMS_API_ORIGIN to the same host.
Where is the open-source skill pack?
The canonical bcms and bcms-content skills live in the bcms/ai repository on GitHub, with bundled reference docs and the content CLI runtime. github.com/bcms/ai
Where can I get support?
Email support [at] thebcms.com or join the BCMS Discord community for help with MCP setup. Join Discord
Start free
Install the skills, connect MCP, and start managing content in minutes.
14-day free trial · No credit card required



