MCP Server - ContentHero

The hosted MCP server exposes the full ContentHero surface at https://mcp.contenthero.ai over OAuth. It is the preferred transport for agents: no key handling, account-scoped, one consent flow. Tools appear as mcp__contenthero__*.

Per-host setup

Claude Code
Claude Desktop
Cursor
Codex

claude mcp add --transport http contenthero https://mcp.contenthero.ai

On first use, Claude Code opens the OAuth consent page. Sign in and approve. The tools then appear in your toolset.

Add the server in Settings, Connectors, or edit the config file directly:

{
  "mcpServers": {
    "contenthero": {
      "url": "https://mcp.contenthero.ai"
    }
  }
}

Restart Claude Desktop and complete the OAuth consent when prompted.

Add to your MCP config:

{
  "mcpServers": {
    "contenthero": {
      "url": "https://mcp.contenthero.ai"
    }
  }
}

What you get

The full surface: generation (image, video, audio, board, lip-sync, upscale, transcribe), the pipeline (create, assemble, schedule, publish posts), brand (kit reads and writes, knowledge base), and inspiration (outliers, performance). The model roster is the live modelId enum on the generate tools.

Local development build

If you are developing against ContentHero, a local stdio build is published as @contenthero/mcp. Tools appear under mcp__contenthero-local__* and point at the same backend. Run it with:

npx -y @contenthero/mcp

It needs CONTENTHERO_API_KEY in the environment. The hosted OAuth server is the right choice for everyday use; the local build is for development.

Verifying

Once connected, ask your agent to read your balance (get_balance) or list your brand kits (list_brand_kits). A clean read confirms the connection and your scopes.

​Per-host setup

​What you get

​Local development build

​Verifying

Per-host setup

What you get

Local development build

Verifying