CapaAI and agents
What an AI agent can do with Capa today, which key it needs, and where to connect it.
Agents work with Capa the same way your code does: over the API, with a key you choose. A read-only key lets an agent answer questions about your content and write the code that reads it. A key made for agents lets it build models and entries.
Pick a way in
MCP server
Connect Claude Code, Cursor or Codex to your project with @capacms/mcp.
Agent API
Build models and content from an agent over HTTP.
What an agent can do
| Task | How | Key |
|---|---|---|
| Read entries and explain an error | the MCP server's read tools, or GET /api/entries | any key that reads the project |
| Write a GraphQL query that fits the limits | the MCP server's GraphQL tools, against your project's schema | a key that reads the models it queries |
| Build models and entries | the Agent API | a legacy key with the agent permission. cap_ keys are refused there |
/api/ reads only today: no key can write through it yet. The keys page explains what each key can do, and how to give an agent one that reads a single model.
Docs for agents
Every docs page has a Markdown copy at the same address plus .md, such as /docs/api/entries.md. /llms.txt lists every page, and /llms-full.txt is the whole reference in one file.