Reeling

Reeling MCP server

Official open-source Model Context Protocol (MCP) server for [Reeling](https://reeling.app), 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)

---

🔑 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_...).

1. 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.