---
summary: ScaiCMS ships a Model Context Protocol server so AI agents are first-class
  clients.
title: MCP integration
path: concepts/mcp
status: published
---

# MCP integration

ScaiCMS speaks [MCP](https://modelcontextprotocol.io) natively. Run the
server in `stdio` mode (for desktop agents) or as HTTP, point your agent at
it with an API key + site ID, and the agent gets typed tools for every
significant operation:

| Tool | Action |
|---|---|
| `create_content`, `edit_content`, `find_content` | Content CRUD |
| `manage_content_permissions` | RBAC overrides on a single content item |
| `manage_workflow` | Status transitions |
| `manage_assets` | Asset upload, listing |
| `manage_taxonomy` | Taxonomies and terms |
| `generate_content` | LLM-assisted draft generation |
| `configure_site` | Site settings |
| `manage_users` | User CRUD |
| `manage_search_index` | Reindex, consistency, cleanup |
| `manage_template_packs` | Template pack lifecycle |
| `manage_form_submissions` | Inbox |
| `manage_documentation` | The docs subsystem (a single tool with action dispatch) |

## Connecting

```bash
export SCAICMS_API_KEY=scai_live_…
export SCAICMS_SITE_ID=30847722-…
python -m scaicms.mcp.server   # stdio
```

Auth is the same as REST — same API key, same scopes apply.

## Agent bundle

A self-contained kit lives at `docs/agent-bundle/` (run
`python -m scaicms.scripts.build_agent_bundle` to regenerate it from source).
It contains the agent guide, an OpenAPI subset, the MCP tool JSON-schema,
and concrete request/response examples. Drop the directory or its tarball
into any agent that needs to author documentation.