MCP: How your AI agent talks to Forge
Forge exposes every content operation as an MCP tool. Your AI agent connects once and can create, update, publish, and query content — within the same role system your human editors use.
What your agent can do
Once connected, your AI agent has access to a set of typed tools — one per content operation. Each tool enforces the same validation and role rules as the HTTP API.
| Tool | Role Required | Description |
|---|---|---|
create_post | Author+ | Draft new content entries. |
publish_post | Editor+ | Promote drafts to live status. |
list_posts | Editor+ | Query and filter all entries. |
delete_post | Editor+ | Remove content permanently. |
Connecting to Forge MCP
Forge MCP runs as a stdio server. Add it to your Claude Desktop config or any MCP-compatible client.
{
"mcpServers": {
"forge": {
"command": "forge-mcp",
"args": ["--url", "https://your-forge-site.com/mcp"]
}
}
}Authentication
All MCP tool calls require a bearer token. Tokens are scoped to a role — Author, Editor, or Admin. Create and revoke tokens via the token management tools or the CLI.
Token security
Store bearer tokens in environment variables. Never commit them to version control.
Minimum role
Assign the minimum required role. An Author token can draft but cannot publish.