Reeling

Official registry Other

Social publishing, scheduling and delivery-status tools for Reeling accounts.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http reeling 'https://mcp.reeling.app/mcp' --header 'X-API-Key: <Reeling API key from your account settings>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "reeling": {
            "type": "http",
            "url": "https://mcp.reeling.app/mcp",
            "headers": {
                "X-API-Key": "<Reeling API key from your account settings>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Reeling MCP server
  2. Platform integrations (15 supported channels)
  3. 🛠️ Available MCP Tools (16 Tools)
  4. 🔑 Getting Started
  5. 💻 Configuration Examples
  6. 🤖 Agent integrations
  7. 🧪 Testing Locally
  8. 📄 License
  9. Contributing
  10. Working examples
  11. Architecture
  12. Development and releases
  13. Setup guide preview

Reeling MCP server

Official open-source Model Context Protocol (MCP) server for Reeling, an AI social media scheduler and short-form video publishing platform.

Use Reeling from Claude Desktop, Cursor, Windsurf, OpenClaw, ChatGPT-compatible connectors, or your own MCP client. The server gives an AI agent a controlled interface for cross-platform social publishing, scheduling, analytics, audience comments, and content adaptation.

This repository is the public developer companion for Reeling. It contains the MCP adapter; runnable API examples live in reeling-examples; Reeling's private application, production infrastructure, customer data, and credentials are not part of this repository.

Links: Reeling homepage · AI Plugins & Skills Hub · 15 Channel Integrations · Developer portal · Hosted MCP install · API settings · Pricing


Platform integrations (15 supported channels)

Availability depends on the connected account, app access and current capabilities. TikTok inbox delivery requires finishing in TikTok; X (Companion mode), Reddit (Companion mode), Medium, and Quora use the Reeling Companion Chrome extension to bridge your authenticated browser session. Check the current platform matrix before publishing.

  • 🎵 TikTok
  • 📸 Instagram Reels & Stories
  • ▶️ YouTube Shorts & Video
  • 🦋 Bluesky
  • 🧵 Threads
  • 📌 Pinterest
  • 💼 LinkedIn
  • 🐦 Twitter / X (OAuth 2.0 or Free Companion Bridge)
  • 👽 Reddit (Companion Bridge or Script OAuth + Topic Radar & Spam Shield)
  • ❓ Quora (Companion Bridge + Question Radar & 75-Word Burden-of-Proof Shield)
  • ✍️ Medium (Companion Bridge + AI Cliché & Tag Shield)
  • 📘 Facebook Pages
  • 💬 Discord & Telegram
  • 🐘 Mastodon

🛠️ Available MCP Tools (16 Tools)

Tool NameDescription
reeling_list_projectsLists all projects & workspaces in your Reeling account.
reeling_list_channelsLists all connected channels across all 15 networks with handle names and account status.
reeling_get_channel_optionsRetrieves publishing options for a connected channel, such as Pinterest boards (ID, name, privacy) or TikTok creator options.
reeling_publish_postPublishes or schedules short-form videos, articles, or community answers across targeted platforms (includes Pre-Publish Spam Shield & 3/day, 3/week cadence guard).
reeling_get_post_statusChecks delivery, processing, and publishing status for a specific post.
reeling_discover_community_questionsDiscovers high-intent daily questions on Reddit and Quora matching your topics and returns remaining daily/weekly cadence quota.
reeling_draft_community_answerGenerates a value-first, non-promotional answer for a Reddit or Quora thread and evaluates its 0–100 Pre-Publish Spam & Shadowban score.
reeling_get_analyticsFetches aggregated analytics: total views, likes, comments, impressions, and per-platform breakdown.
reeling_sync_metricsTriggers a live sync against YouTube, Bluesky, Instagram, Threads, and TikTok APIs.
reeling_evaluate_content_jevEvaluates video scripts and captions using Reeling's JEV hook and retention diagnostics.
reeling_get_inboxRetrieves audience comments across social channels into a unified inbox.
reeling_reply_to_commentPosts a direct reply to a comment on any connected social platform.
reeling_adapt_content_aiUses Reeling's AI copy engine to adapt a hook/script for TikTok, Instagram, YouTube, Threads, or Bluesky.
reeling_generate_videoRequests short-form video generation through Reeling’s configured service; plan allowance and provider processing apply.
reeling_create_storyboardGenerates structured multi-scene storyboards (30s up to 5 minutes) broken into consecutive 5s cinematic cuts with audio/foley cues.
reeling_stitch_storyboardRequests scene rendering and stitching through Reeling’s configured video workflow.

🔑 Getting Started

  1. Obtain your API Key:
    • Go to reeling.app and sign in.
    • Navigate to Settings → API Keys.
    • Generate a new key (starts with rl_...).
  2. Run the server:

     npx -y github:yomariano/reeling-mcp#v1.1.0

    Or connect to the hosted Streamable HTTP endpoint at https://mcp.reeling.app/mcp using the installation guide.


💻 Configuration Examples

1. Claude Desktop

Add this to your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "reeling": {
      "command": "npx",
      "args": ["-y", "github:yomariano/reeling-mcp#v1.1.0"],
      "env": {
        "REELING_API_KEY": "rl_your_live_api_key_here",
        "REELING_API_URL": "https://api.reeling.app"
      }
    }
  }
}

Or run directly from source:

{
  "mcpServers": {
    "reeling": {
      "command": "node",
      "args": ["/absolute/path/to/reeling-mcp/bin/cli.js"],
      "env": {
        "REELING_API_KEY": "rl_your_live_api_key_here"
      }
    }
  }
}
2. Cursor IDE

Create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "reeling": {
      "command": "npx",
      "args": ["-y", "github:yomariano/reeling-mcp#v1.1.0"],
      "env": {
        "REELING_API_KEY": "rl_your_live_api_key_here"
      }
    }
  }
}
3. Antigravity (AGY)

Add to your ~/.gemini/antigravity-cli/mcp_config.json or project MCP configuration:

{
  "mcpServers": {
    "reeling": {
      "command": "node",
      "args": ["/absolute/path/to/reeling-mcp/bin/cli.js"],
      "env": {
        "REELING_API_KEY": "rl_your_live_api_key_here"
      }
    }
  }
}
4. Remote Hosted SSE Server (for Grok Bot, Claude Remote, Web Agents)

You can run reeling-mcp as a persistent Server-Sent Events (SSE) server for remote AI agents:

# Run locally or deploy to Railway / Render / VPS / Docker
npx -y github:yomariano/reeling-mcp#v1.1.0 --sse --port 3005

Endpoints exposed:

  • GET /health: Health check status.
  • GET /sse: Server-Sent Events connection stream (provide a credential through your client’s secret header configuration).
  • POST /messages?sessionId=...: JSON-RPC protocol message receiver.
Grok Bot Configuration (xAI)

Add to your Grok Bot custom MCP servers:

  • Transport: SSE
  • Endpoint: https://mcp.reeling.app/sse (or http://localhost:3005/sse)
  • Headers: X-API-Key: rl_your_live_api_key_here

🤖 Agent integrations

The hosted server exposes installable bundles and connector metadata for ChatGPT-compatible connectors, Claude, and Grok at mcp.reeling.app/install. The local package works with any MCP client that can launch an npm package or connect to the HTTP transport.

For API-level integrations, see the Reeling developer portal. Please open an issue when you build a client, example, or platform adapter that other Reeling users could reuse.


🧪 Testing Locally

You can test the MCP server manually using the MCP inspector:

npx @modelcontextprotocol/inspector node bin/cli.js

Or test SSE mode:

node bin/cli.js --sse --port 3005
curl http://localhost:3005/health

📄 License

MIT © reeling.app

Contributing

Issues and pull requests are welcome for client compatibility, documentation, examples, and safe improvements to the MCP transport. Do not commit API keys, production URLs containing secrets, customer data, or private Reeling application code. See the repository's security policy before reporting a vulnerability.

Working examples

Clone reeling-examples for account discovery, a reviewed video request, bounded delivery-status polling, analytics retrieval and an editable content calendar. Start in offline mode. Read the example guide.

Architecture

flowchart LR
  Client[Your MCP client] -->|stdio or HTTPS /mcp| Adapter[Reeling MCP adapter]
  Adapter -->|API key| API[Reeling REST API]
  API --> Queue[Publishing queue]
  Queue --> Channels[Authorized social channels]
  API -->|Per-destination state| Adapter

The adapter sends authenticated requests to the Reeling API. Account, plan and platform permissions determine what can run. Review write tools in your client; a tool result or upload receipt alone does not establish public publication.

Development and releases

npm ci
npm test
npm run check
npm pack --dry-run

See CONTRIBUTING.md, CHANGELOG.md, and GitHub releases. Installs above use a versioned GitHub tag; npm publication requires a separate authenticated npm release.

Setup guide preview

Local preview of the public developer guide. Open the current setup guide.

Frequently asked questions

What is Reeling?

Social publishing, scheduling and delivery-status tools for Reeling accounts.

How do I install Reeling?

It runs as a remote server. In Claude Code: claude mcp add --transport http reeling 'https://mcp.reeling.app/mcp' --header 'X-API-Key: <Reeling API key from your account settings>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Reeling need an API key?

Yes. It expects X-API-Key, which you set in its configuration.

Is Reeling open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Reeling?

It is published by yomariano. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.