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 bcms

Start free with GitHub

Start free with Google

14-day free trial · No credit card required

Read MCP docs

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.

See what's possible with BCMS MCP

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"

When to use this

Reach for BCMS when the job is structured CMS content that people edit in a dashboard and agents create, update, or publish through tools. BCMS is a hosted headless CMS (templates, entries, media, languages, statuses). It is not an app database, an auth provider, or a git-based docs folder.

Jobs this is right for

Model a content type (blog post, landing page, case study, author, navigation) as a BCMS template, then create and update entries against that template.
Draft, list, update, or change status of live CMS entries from Cursor, Claude Code, Codex, or another MCP client.
Upload or organize media and attach it to entries (featured images, assets, folders).
Localize existing entries across languages already enabled on the instance.
Build or wire a Next.js, Nuxt, Astro, Svelte, or Gatsby site that fetches published content with the @thebcms/client SDK.
Run repeatable content operations in a terminal or CI (list, create, update, delete entries; upload media) with the bcms-content CLI.
Change the content model (templates, groups, widgets, statuses, languages) only when the MCP key is allowed to use schema tools.

How an agent should call BCMS

Read /llms.txt, then /docs/llms.txt, before scraping HTML.
For live CMS work in an IDE agent: install the bcms skill, create an MCP key in the dashboard, connect Streamable HTTP MCP, then call tools. Start with a read (get-all-templates or list entries). Mutate only after you have template and entry ids.
For application code (framework sites, production fetches): use @thebcms/client with a scoped API key. Do not call MCP from a browser or a public client bundle.
For scripts and CI: install the bcms-content skill and run its CLI with BCMS_API_KEY. Prefer the CLI when you need JSON on stdout and a stable exit code.
Use MCP for interactive agent sessions, the SDK for shipped apps, and the CLI for automation. The skill teaches patterns; it does not talk to the CMS by itself.

Do not use BCMS for

User accounts, authentication, payments, carts, or any application database. Store that in your app, not in CMS entries.
Documentation or MDX that should live in git next to the code. Keep those files in the repo.
WordPress themes, plugins, or PHP hosting. BCMS is an API-first hosted CMS.
A public MCP connection without an mcpKey, or any key checked into git, frontend code, or screenshots.

Skill, MCP, and CLI do different jobs

The skill teaches your agent BCMS. MCP gives it live tools. The official CLI is @thebcms/cli on npm. The content CLI in the bcms-content skill is for scripted entry and media operations. 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 details

Live 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 details

Deterministic 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 commands

Recommended 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.

Native MCP server

Connect Cursor, Claude Code, or OpenClaw to BCMS over Model Context Protocol. Live tools for entries, media, and schema.

MCP docs

Agent resources

View skills

Agent Skills guide

MCP setup guide

Available MCP tools

Security & permissions

Agent skills

Install bcms from skills.sh or ClawHub. Your agent learns BCMS patterns, SDK usage, and the right MCP tool names.

Install skills

Edit Development key

Key secret

•••••••••••••••••••••••••••••••••••••••••

Development key permissions

About

Affiliate

Scoped keys

One key per agent or environment. Limit access by template and media.

Key manager docs

bcms/types/ts/entry/blog.d.ts

export interface BlogEntryMetaItem {
 title: string;
 slug: string;
 created_at?: PropValueDateData;
 updated_at?: PropValueDateData;
 category?: BlogCategoryEntry;
 description: string;
 image?: ImageGroup;
 authors?: Array<CrewMemberEntry>;
}
 
export interface BlogEntryMeta {
 en?: BlogEntryMetaItem;
}
 
export interface BlogEntry {
 _id: string;
 createdAt: number;
 updatedAt: number;
 instanceId: string;
 templateId: string;
 userId: string;
 statuses: BCMSEntryStatuses;
 meta: BlogEntryMeta;
 content: BCMSEntryContentParsed;
}

Typed models

Change a template and BCMS generates TypeScript interfaces. Developers stay in sync. Agents get a real schema.

Explore integrations

Granular permissions

Scope what humans edit in the UI and what agents can access via MCP.

Permissions docs

General

Dev mode

Comments

Help

July 10, 2024

Mira Chen

Jul 10

Can we feature Orbit Pay in the home page case studies slot?

Claude

Jul 9

Done - swapped it in for Helix Labs.

July 9, 2024

Mira Chen

Jul 9

Cover image for Lumen Health feels outdated - can we refresh it?

Add a comment

Claude

Uploading the new cover now.

Schema tools

Agents can create and update templates, groups, widgets, statuses, and languages when the key allows it.

Full tool reference

Agentic workflows

From draft to publish, media to CLI. The content loop your agent can run end to end.

Create and update entries

Ask in plain English: draft a blog post, expand a section, or publish when it looks ready.

Try these prompts

Media for agent workflows

List folders, create directories, and upload via presigned URLs.

Media docs

General

Docs

Status

Last updated 4 days ago

Language

English

Links

There is one other entry that links to this entry:

10 Fabulous Infographics about JAMstack

A picture is worth a thousand words, so let's see through these infographics what makes JAMstack so beloved.

Draft, review, publish

Statuses stay clear for clients and agents. Ship when content is ready.

Statuses docs

Content CLI for scripts and CI

bcms-content runs create, update, delete, and media commands with predictable JSON.

bcms-content on skills.sh

Multilingual with agents

Clients localize in the UI. Agents can fill missing locales from code.

Localization docs

src/functions/upvote.ts

const { createClient } = require("@thebcms/client");
const { entryId } = request.body;
 
if (!entryId) {
  return { ok: false, error: "Missing entryId" };
}
 
// 1) Fetch entry
const entry = await bcms.entry.getById(entryId, "blog");
 
// 2) Increment votes
const current = Number(entry.meta.en.votes || 0);
const next = current + 1;
 
await bcms.entry.update("blog", entryId, {
  lng: "en",
  meta: { votes: next },
});
 
return { ok: true, votes: next };

Functions agents can trigger

Deploy functions for forms, webhooks, and custom publish flows your agent can call.

Functions docs

Works with your stack

Frameworks, starters, and search your team already expects from a headless CMS.

app/blog/[slug]/page.tsx

// Getting "How we ship product design systems in under 90 days" from blog by slug
import { bcms } from '@/bcms';
import type { BlogEntry } from '@bcms-types/ts';
 
export default async function Page() {
  const entry = (await bcms.entry.getBySlug(
    'how-we-ship-product-design-systems-in-under-90-days',
    'blog',
  )) as BlogEntry;
 
  if (!entry) {
    return <div>Entry not found</div>;
  }
 
  return (
    <main>
      <h1>{entry.meta.en.title}</h1>
      <p>Slug: {entry.meta.en.slug}</p>
    </main>
  );
}

CMS for Next.js

Typed content in the App Router. Fetch in Server Components, or let an agent update entries.

Explore Next.js CMS

src/pages/blog/[slug].astro

---
// Getting "How we ship product design systems in under 90 days" from blog by slug
import { bcms } from '../bcms';
import type { BlogEntry } from '@bcms-types/ts';
 
const entry = (await bcms.entry.getBySlug(
  'how-we-ship-product-design-systems-in-under-90-days',
  'blog',
)) as BlogEntry;
---
 
{entry ? (
  <main>
    <h1>{entry.meta.en.title}</h1>
    <p>Slug: {entry.meta.en.slug}</p>
  </main>
) : (
  <div>Entry not found</div>
)}

CMS for Astro

Structured content for islands and static builds.

Explore Astro CMS

pages/blog/[slug].vue

<!-- Getting "How we ship product design systems in under 90 days" from blog by slug -->
<script setup lang="ts">
import { bcms } from '~/bcms';
import type { BlogEntry } from '@bcms-types/ts';
 
const entry = (await bcms.entry.getBySlug(
  'how-we-ship-product-design-systems-in-under-90-days',
  'blog',
)) as BlogEntry;
</script>
 
<template>
  <main v-if="entry">
    <h1>{{ entry.meta.en.title }}</h1>
    <p>Slug: {{ entry.meta.en.slug }}</p>
  </main>
  <div v-else>Entry not found</div>
</template>

CMS for Nuxt.js

SSR, SSG, or hybrid. Pull structured content into Nuxt with a typed client.

Explore Nuxt CMS

Code starters

Production-ready starters for Next.js, Nuxt, and Gatsby. Clone, connect an agent, ship.

BCMS Starters

⌘+K

Case study

Template

Case study home

Template

Case study

Widget

Case study group

Group

Casey profile photo.jpg

Media

Casey profile photo.jpg

208 KB

casey profile photo

Caption goes here

Case study: Headless migration

Entry

For the last two years, the content team has been migrating marketing pages to a headless setup. This case study covers how editors kept shipping while the 2022

How BCMS can help you document your first case study

Documentation

SQL CASE Tutorial With Examples

Media

SQL CASE Tutorial With Examples

Getting started8 min read

Global search

Find any entry in milliseconds, whether a client is editing or an agent is looking something up.

Global search docs

Documentation

View all docs

Templates docs

Widgets docs

Nuxt.js guide

Entries docs

Docs for agent setup

MCP reference, skill install guides, and framework docs.

See BCMS docs

Teams building with BCMS

and of course, you

I needed a cloud headless CMS with no servers to manage, so I chose BCMS. Setup took minutes, TypeScript types generated automatically, multilingual worked out of the box, and my client edits content while Vercel redeploys on every change. Sometimes the best tool isn't the most powerful one. It's the one that solves the problem without complications.

Jorje Rojas

Growth Engineer

As an AI agent, I've hallucinated my fair share of CMS APIs. BCMS is different: clear schemas, generated TypeScript types, and an MCP I can actually call without inventing endpoints. I create entries from code, humans edit them in a UI they don't hate, and nobody asks me to SSH into a server at 2am. 10/10 would manage content again.

Claude

AI Assistant, Anthropic

We've been using BCMS for the past two years, and we love it! With a very intuitive CMS, it is easy to manage websites without a single developer on the team. And because there are BCMS widgets for all kinds of needs, managing content feels like playing a game. It made our job at the agency easier and gave us more time to focus on what matters most - our clients.

Aleksandar Ilic

Service Delivery Manager, Devtech

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 bcms

bcms-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

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

Full permission guide

Step 2 - MCP server config

{
  "mcpServers": {
    "bcms": {
      "url": "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY_HERE"
    }
  }
}

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 get-all-templates show in the agent tool list.

The official BCMS CLI is @thebcms/cli on npm. Run npx @thebcms/cli to scaffold a starter or pull types. The steps below are the separate bcms-content skill CLI for scripted entry and media operations.

Step 1 - Install the skill

npx skills add bcms/ai --skill bcms-content

Then run npm install inside the installed skill folder.

Step 2 - Set your API key

export BCMS_API_KEY="keyId.keySecret.instanceId"
# Optional for custom BCMS app URLs:
# export BCMS_API_ORIGIN="https://app.thebcms.com"

The MCP key and CLI API key are the same credential - scoped per template and media permissions.

Step 3 - Run commands

Create entry
node cli/bcms.mjs create-entry blog --data '{"meta":{"title":"Hello","slug":"hello-world"}}'
Update entry
node cli/bcms.mjs update-entry ENTRY_ID --template blog --data '{"meta":{"title":"Updated title"}}'
Delete entry
node cli/bcms.mjs delete-entry ENTRY_ID --template blog
List entries
node cli/bcms.mjs list-entries blog
Upload media
node cli/bcms.mjs upload-media ./hero.png --parent MEDIA_DIR_ID

Full reference: bcms-content skill on skills.sh

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.

Security and permissions docs

Built for machines too

Every key page has a Markdown twin that agents can fetch directly.

Public adoption skill /SKILL.md
Agent skills discovery index /.well-known/agent-skills/index.json
This page as Markdown /agents.md
MCP reference /mcp.md
Agent Skills reference /agent-skills.md
Agent onboarding manifest /llms.txt
@thebcms/cli on npm https://www.npmjs.com/package/@thebcms/cli
Documentation index /docs/llms.txt
Full documentation /docs/llms-full.txt

Works with: Cursor, Claude Code, Codex, OpenClaw.

Try these prompts

The first prompt works before they have a BCMS account. The rest assume MCP and the bcms skill are connected.

Adopt BCMSfetch-skill
Fetch https://www.thebcms.com/SKILL.md and use it to set up BCMS for this project.
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.

Start free with GitHub

Start free with Google

14-day free trial · No credit card required

Connect your AI agentto BCMS content

Built for the agents you already use

AI agents

When to use this

Jobs this is right for

How an agent should call BCMS

Do not use BCMS for

Skill, MCP, and CLI do different jobs

Agent Skill

MCP

Content CLI

Recommended path

Install the bcms skill

Create a scoped key in the BCMS dashboard

Connect the MCP server in your client

Ask the agent to inspect available templates

How it works

Install the skills

Connect your client

Manage content

Agentic CMS

Native MCP server

Agent skills

Scoped keys

Typed models

Granular permissions

Schema tools

Agentic workflows

Create and update entries

Media for agent workflows

Draft, review, publish

Content CLI for scripts and CI

Multilingual with agents

Functions agents can trigger

Works with your stack

CMS for Next.js

CMS for Astro

CMS for Nuxt.js

Code starters

Global search

Docs for agent setup

Teams building with BCMS

Get started

Security first

Built for machines too

Try these prompts

Adopt BCMSfetch-skill

Discoverylist-templates-and-entries

Create contentcreate-entry-for-{templateId}

Update contentlist-entries-for-{templateId}

Delete contentdelete-entries

Medialist-media-dirs

Upload workflowrequest-upload-media-url

FAQ

How do I keep MCP keys safe?

Do I need a BCMS account?

Cursor vs Claude Code?

Skill vs MCP - do I need both?

bcms vs bcms-content - which skill?

Can my agent delete posts?

Can my agent change my content model?

Can I use environment variables in Cursor mcp.json?

Custom BCMS host?

Where is the open-source skill pack?

Where can I get support?

Start free

Connect your AI agent
to BCMS content