ContentImage

MCP setup

Last updated:

The ContentImage MCP server is at https://contentimage.io/api/mcp, uses Streamable HTTP and authenticates with a bearer API key. It exposes twelve tools for rendering images, managing brands and sites, and approving results. OAuth sign-in is not available yet.

Claude Code

claude mcp add --transport http contentimage https://contentimage.io/api/mcp \
  --header "Authorization: Bearer ci_..."

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "contentimage": {
      "url": "https://contentimage.io/api/mcp",
      "headers": { "Authorization": "Bearer ci_..." }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "contentimage": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://contentimage.io/api/mcp", "--header", "Authorization: Bearer ci_..."]
    }
  }
}

Tools

  • list_sites: sites with agent setting, mode, CMS and language.
  • get_brand, set_brand, draft_brand_from_url: read, change or draft a brand kit from a URL. set_brand only changes the fields you pass.
  • render_image: images for one article, with inline previews. Accepts an inline brand.
  • bulk_render: up to 10 article URLs in one call.
  • list_images, approve_image, reject_image: review drafts.
  • set_agent: turn the agent on or off and set auto or approve mode.
  • sweep_site: queue a backfill for posts without an image.
  • delete_site: delete a site with its images and brand kit.

FAQ

Which transport does it use?
Streamable HTTP, stateless, at /api/mcp. JSON responses, no session.
Is there OAuth?
Not yet. Use an API key.