Overview

The Content Rabbit MCP server exposes your team through the Model Context Protocol. An AI assistant that speaks MCP can list and manage posts, schedule and publish content, generate text and hashtags, and read analytics — all scoped to the team that owns the API key.

The server uses Streamable HTTP transport in stateless mode:

• POST /api/v1/mcp — JSON-RPC messages (initialize, tools/list, tools/call, …)
• GET /api/v1/mcp — Server-Sent Events stream for server-initiated messages
• DELETE /api/v1/mcp — Close the session

Every tool call runs under the same tenant scope and authorization checks as the public REST API. See the Content Rabbit API for REST equivalents and the Terminology glossary for team and platform terms.

API keys are team-scoped. A key can only read or mutate data in the team it was issued for. Rotate keys regularly and delete unused keys immediately.

Endpoint

https://<your-domain>/api/v1/mcp

https://<your-domain>/api/v1/mcp

In production this is https://contentrabbitai.com/api/v1/mcp. The server handles MCP over Streamable HTTP with enableJsonResponse: true and no server-persisted session.

Authentication

All requests must include a Bearer API key:

Authorization: Bearer YOUR_API_KEY

Authorization: Bearer YOUR_API_KEY

The server authenticates with the same Authorization: Bearer <key> mechanism as the public REST API, and rejects a missing or invalid key with 401 Unauthorized. Your API key scopes every tool call to its team and plan.

Getting an API key

1. Open Settings > Team.
2. Choose the team you want to automate.
3. Go to the API & Integrations tab and press Generate API key.
4. Copy the value immediately — you can always rotate to get a fresh key.

Sandbox keys (metadata.sandbox === true) simulate mutating tools and never write to the database or call external services. Read tools run normally against the sandbox team's data.

Rate limiting

The MCP endpoint shares the same plan-tiered, per-team rate limit as the public REST API. Inspect response headers to track usage:

Exceeding limits returns 429 Too Many Requests. Retry with exponential backoff.

Connect an MCP client

Any MCP client that supports Streamable HTTP works. Configure the server URL plus an Authorization header with your API key. The shape varies by client — the fields below are the portable part:

{
  "mcpServers": {
    "content-rabbit": {
      "url": "https://contentrabbitai.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "content-rabbit": {
      "url": "https://contentrabbitai.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

For clients that split transport options, use:

• Transport: http / streamable-http
• URL: https://contentrabbitai.com/api/v1/mcp
• Header: Authorization: Bearer YOUR_API_KEY

Test the connection by listing tools (tools/list) — you should see 39 tools. A 401 means the key is missing, revoked, or pasted with extra whitespace.

Available tools

Both MCP servers — this hosted server and the stdio npm package @contentrabbit/mcp-server — mount one shared tool registry, so the same 39 tools exist on both. All tools are scoped to the caller's team. Only these tools exist — the server exposes no other names.

Posts

Teams

Accounts

Queue

Webhooks

Utility

Generate

Media

Analytics

Tool responses are JSON text payloads. Mutating tools called with a sandbox key return a simulated success with sandbox: true and a synthetic id (<prefix>_sandbox_<uuid>) without touching the database or external accounts.

Related articles

• Content Rabbit API — REST base URL, pagination, error format, and quick-start examples.
• Terminology — Team and platform definitions.
• Connecting Social Accounts — Connect and reconnect the accounts that posts_publish targets.