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.
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
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 draft posts, upload media, or publish entries. Or run CLI commands that return JSON.
Install the skills
Copy an install command for your registry. Most teams start with bcms; add bcms-content for terminal workflows.
bcms v1.3.1
bcms-content v1.0.0
- 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
Connect MCP
Generate a scoped MCP key in your BCMS dashboard, then paste the config into your AI client.
Step 1 - Create MCP key
- Open BCMS dashboard - Settings - MCP
- Create MCP key with least-privilege scopes per template
- Copy the three-part key:
keyId.keySecret.instanceId
Step 2 - MCP server config
Step 3 - Client setup
- Open Settings - MCP - Add server.
- Paste the JSON config above with your MCP key, or add the URL manually.
- Restart MCP or reload the window if tools do not appear.
- Confirm tools like list-templates-and-entries show in the agent tool list.
Content CLI (bcms-content)
Run create, update, delete, and media commands from the terminal with predictable JSON output.
Step 1 - Install the skill
Then run npm install inside the installed skill folder (it ships its own package.json).
Step 2 - Set your API key
The MCP key and CLI API key are the same credential - scoped per template and media permissions.
Step 3 - Run commands
List entries
Create entry
Update entry
Delete entry
Upload media
Full reference: bcms-content skill on skills.sh · github.com/bcms/ai/skills/bcms-content
Try these prompts
Works after MCP and the bcms skill are connected. Copy a prompt and paste it into your agent.
Discovery
Expected: list-templates-and-entries
Create content
Expected: create-entry-for-{templateId}
Update content
Expected: list-entries-for-{templateId}
Delete content
Expected: delete-entries
Media
Expected: list-media-dirs
Upload workflow
Expected: request-upload-media-url
Internal links
Expected: get-entry-pointer-link
Audit
Expected: list-entries-for-{templateId}
Publish
Expected: update-entry-for-{templateId}
What your agent can do
What MCP can do when your key has the right scopes. Full tool list lives in the docs.
| Capability | MCP | Notes |
|---|---|---|
| List templates & entries | Yes | list-templates-and-entries, list-entries-for-{templateId} |
| Create entries | Yes | create-entry-for-{templateId} |
| Update entries | Yes | update-entry-for-{templateId} |
| Delete entries | Yes | delete-entries (scoped key with delete permission) |
| List / organize media | Yes | list-all-media, list-media-dirs, create-media-directory |
| Upload media | Yes | request-upload-media-url (presigned URL workflow) |
| Internal rich-text links | Yes | get-entry-pointer-link, get-media-pointer-link |
| Edit templates / schema | Yes | Full schema CRUD - templates, groups, widgets, statuses, languages |
For developers
Building with Next.js, Nuxt, or Astro? The bcms skill covers the SDK, templates, and framework guides. Use MCP or bcms-content when your agent needs to change live content.
Security
- Create dedicated MCP/API keys per person or environment; never reuse admin keys.
- Use least-privilege template and media scopes when creating keys.
- Never put MCP keys or BCMS_API_KEY in frontend code, public repos, or shared screenshots.
- Rotate keys immediately if they are exposed.
- MCP requests share API rate limits - see the MCP docs for details.
FAQ
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.
Same MCP URL and JSON config. Install bcms (and optionally bcms-content) in either client with npx skills add bcms/ai --skill bcms.
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 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.
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.
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.
Unreliable. Cursor does not consistently expand env vars in MCP server URLs. Paste your key in local, user-level config only.
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.
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/aiEmail [email protected] or join the BCMS Discord community for help with MCP setup.
Join DiscordGet your agent connected to BCMS
Install the skills, connect MCP, and start managing content in minutes.
Questions? Join Discord