Skip to content
Developers & agents

Built for developers and agents

Content Rabbit runs headless. One REST API, a 97-tool MCP server, a CLI, an npm SDK, every major automation connector, and webhooks, across 36 platforms. Wire it into your code, your agent, or a no-code flow, then let it publish.

36platforms to publish
97MCP tools
4automation connectors
1key across every surface

Three ways to drive it

Call the API

Create, schedule, publish, and read analytics over HTTP from any backend. OpenAPI spec, Bearer auth, one POST to get a key.

Add the MCP server

Point Claude, Codex, Cursor, or any MCP client at one HTTPS URL. 97 tools cover the whole content workflow.

Message a bot

Drive Content Rabbit from a chat. Connect the Telegram, Discord, or Slack bot and talk to your content agent where you already work.

Call it in three lines

Get a key
# Create an account and key with one call — no dashboard
curl -X POST https://contentrabbitai.com/api/v1/agent/signup \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com"}'
Publish over REST
# Schedule a post to three platforms
curl -X POST https://contentrabbitai.com/api/public/v1/posts \
  -H "Authorization: Bearer $CONTENT_RABBIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Shipping day.",
    "platforms": ["twitter", "linkedin", "bluesky"],
    "scheduledAt": "2026-09-01T15:00:00Z"
  }'
Add the MCP
# Add the MCP server to Claude Code — 97 tools
claude mcp add --transport http content-rabbit \
  https://contentrabbitai.com/api/v1/mcp \
  --header "Authorization: Bearer $CONTENT_RABBIT_KEY"

The whole surface

Every entry point is a first-party product. Pick the one that fits how you build.

REST API

Versioned endpoints for posts, text generation, media, and analytics. OpenAPI spec, Bearer tokens.

API reference

97-tool MCP server

Hosted at one URL and shipped as a stdio npm package. Both transports expose the same 97 tools.

MCP setup

CLI

Script your content workflow from the shell with the rabbit command. Same key as everything else.

Developer overview

npm SDK

Typed methods for every endpoint in the @contentrabbit package. Install it and start calling.

Developer overview

Automation connectors

Wire posts into no-code flows with n8n, Zapier, and Pipedream, plus Make (in review).

Integrations

Agent plugins

First-party plugins for Codex and Claude Code so your coding agent can publish as it works.

Claude Code

Webhooks

Get event push when a post publishes or fails. No polling loop to run on your side.

API reference

One API key

A single workspace-scoped key works across REST, MCP, CLI, and SDK. Provision it headless.

Get a key

Every major automation connector

Build a flow in the tool you already use. Content Rabbit ships a native app for n8n, Zapier, and Pipedream, with Make in review.

n8n
Make
Zapier
Pipedream

FAQs

What can I build on Content Rabbit?

Anything that touches your content pipeline. Draft, schedule, and publish posts from your own app or agent, generate text and hashtags, list media, and read analytics. Every one of those runs through the REST API, the MCP server, the CLI, or the SDK.

REST, MCP, CLI, or SDK: which do I use?

Use the REST API or SDK when your own backend does the work. Use the MCP server when an AI assistant should drive Content Rabbit. Use the CLI to script from the shell. Every surface takes the same API key.

How do I get an API key?

Create an account and key with one POST. No dashboard, no email step:

curl -X POST https://contentrabbitai.com/api/v1/agent/signup -H 'Content-Type: application/json' -d '{"email":"you@example.com"}'

The response shows your key once. Store it, then send it as the Authorization: Bearer token on every call.

Which platforms can I publish to?

36, including X, LinkedIn, Instagram, TikTok, YouTube, Threads, Bluesky, Mastodon, Pinterest, Reddit, Discord, Telegram, and more. One request can target several at once.

Do you have automation connectors?

Yes: n8n, Zapier, and Pipedream, plus Make (in review). You can wire Content Rabbit into a no-code flow without writing API calls by hand.

Give your agent the whole content workflow

One key works across the API, the MCP server, the CLI, and the SDK. Provision it headless and start publishing.