# Reeling MCP server

> Publish and schedule social posts and short videos across 15 channels, read analytics and inbox comments, and draft community replies.

- Listing: https://mcp.tc/i/reeling
- Connect: use the server's own URL `https://mcp.reeling.app/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: Reeling
- Homepage: <https://reeling.app/developers/mcp>
- Repository: <https://github.com/yomariano/reeling-mcp>

## About

Connects an AI assistant to a Reeling account for cross-platform publishing to TikTok, Instagram Reels, YouTube Shorts, Threads, Bluesky, X, LinkedIn, Pinterest, Reddit, Quora, Medium and more. Tools cover scheduling, delivery status, analytics, a unified comment inbox, replies, AI copy adaptation, storyboards, video generation and pre-publish spam scoring.

Runs as a hosted Streamable HTTP endpoint at mcp.reeling.app/mcp, or locally with npx (Node.js 22+). A Reeling API key is required, sent in the X-API-Key header or as REELING\_API\_KEY. Two discovery tools work without a key. MCP and API access are tied to paid Reeling plans.

## What it can do

- Publish or schedule posts and videos across multiple social platforms
- Check delivery status and fetch aggregated analytics
- Read the unified comment inbox and reply to comments
- Discover Reddit and Quora questions and draft community answers
- Score drafts for spam risk before publishing
- Adapt a hook or script into platform-specific copy
- Generate short videos and multi-scene storyboards

## Tools (20)

- `reeling_get_platform_matrix`: Return supported platforms, auth methods, limits and pricing tiers; no key needed.
- `reeling_check_spam_score`: Score a draft for spam risk on Reddit, Quora, Medium, LinkedIn or X; no key needed.
- `reeling_list_projects`: List projects and workspaces in the Reeling account.
- `reeling_list_channels`: List connected social channels with usernames and statuses.
- `reeling_publish_post`: Publish or schedule videos, articles and posts across platforms.
- `reeling_discover_community_questions`: Find Reddit and Quora questions matching keywords and check cadence counters.
- `reeling_draft_community_answer`: Draft a value-first reply for X, Reddit or Quora.
- `reeling_schedule_community_autopilot`: Schedule daily reply-only Reddit comments across target subreddits.
- `reeling_humanize_content`: Rewrite a draft to remove AI-sounding phrasing.
- `reeling_get_channel_options`: Get publishing options such as Pinterest boards or TikTok settings.
- `reeling_get_post_status`: Get delivery and publishing status of a post per network.
- `reeling_get_analytics`: Fetch views, likes, comments, impressions and top posts.
- `reeling_sync_metrics`: Trigger an on-demand metrics sync from platform APIs.
- `reeling_evaluate_content_jev`: Diagnose published post metrics for hook, engagement and drop-off.
- `reeling_get_inbox`: Fetch audience comments across connected platforms.
- `reeling_reply_to_comment`: Send a direct reply to a comment on a social network.
- `reeling_adapt_content_ai`: Turn one hook, script or topic into platform-tailored copy.
- `reeling_generate_video`: Generate a short video from a prompt and return its media URL.
- `reeling_create_storyboard`: Create a multi-scene storyboard in 5-second cuts.
- `reeling_stitch_storyboard`: Render storyboard scenes and stitch them into one MP4.

## Example prompts

- "List my Reeling projects and connected channels"
- "Schedule this video to TikTok and YouTube Shorts for tomorrow at 9am"
- "Check the spam score of this Reddit post draft"
- "Show analytics for my posts over the last 30 days"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http reeling https://mcp.reeling.app/mcp --header "X-API-Key: <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "reeling": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.reeling.app/mcp",
        "--header",
        "X-API-Key: <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Reeling&connectorUrl=https%3A%2F%2Fmcp.reeling.app%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.reeling.app/mcp`. Under **Request headers**, add `X-API-Key: <YOUR_API_KEY>` with your key from Reeling, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=reeling&config=eyJ1cmwiOiJodHRwczovL21jcC5yZWVsaW5nLmFwcC9tY3AiLCJoZWFkZXJzIjp7IlgtQVBJLUtleSI6IjxZT1VSX0FQSV9LRVk%2BIn19>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "reeling": {
      "url": "https://mcp.reeling.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "reeling": {
      "type": "http",
      "url": "https://mcp.reeling.app/mcp",
      "headers": {
        "X-API-Key": "${input:x-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-api-key",
      "description": "X-API-Key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "reeling": {
      "serverUrl": "https://mcp.reeling.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add reeling --url https://mcp.reeling.app/mcp
```

`codex mcp add` can’t set the `X-API-Key` header, so this step is required: put this entry in `~/.codex/config.toml` instead of running the command, or add its `env_http_headers` line to the entry the command made:

`config.toml`:

```toml
[mcp_servers.reeling]
url = "https://mcp.reeling.app/mcp"
env_http_headers = { "X-API-Key" = "X_API_KEY" }
```

Codex reads the header values from the environment variables named in `env_http_headers`.

### Gemini CLI

```bash
gemini mcp add --transport http --header "X-API-Key: <YOUR_API_KEY>" reeling https://mcp.reeling.app/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "reeling": {
      "type": "http",
      "url": "https://mcp.reeling.app/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.reeling.app/mcp`.

## Recent changes

- 2026-11-09 17:26 UTC: Tracking started: 20 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/reeling#history (Atom feed: https://mcp.tc/i/reeling/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-10 (reachable)
- Listed: 2026-11-09
- Updated: 2026-11-09

---
Source: https://mcp.tc/i/reeling (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
