Skip to main content
Glama
Reeling MCP

Reeling MCP

README.md
# Reeling MCP server

[![MCP checks](https://github.com/yomariano/reeling-mcp/actions/workflows/test.yml/badge.svg)](https://github.com/yomariano/reeling-mcp/actions/workflows/test.yml)
[![GitHub release](https://img.shields.io/github/v/release/yomariano/reeling-mcp)](https://github.com/yomariano/reeling-mcp/releases)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
[![Glama validation](https://glama.ai/mcp/servers/yomariano/reeling-mcp/badges/score.svg)](https://glama.ai/mcp/servers/yomariano/reeling-mcp)

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](https://github.com/yomariano/reeling-examples); Reeling's private application, production infrastructure, customer data, and credentials are not part of this repository.

**Links:** [Reeling homepage](https://reeling.app) · [AI Plugins & Skills Hub](https://reeling.app/plugins) · [15 Channel Integrations](https://reeling.app/integrations) · [Developer portal](https://reeling.app/developers) · [Hosted MCP install](https://mcp.reeling.app/install) · [API settings](https://reeling.app/settings?tab=api) · [Pricing](https://reeling.app/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](https://reeling.app/reeling-companion.zip) to bridge your authenticated browser session. Check the [current platform matrix](https://reeling.app/integrations) 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 Name | Description |
|---|---|
| `reeling_list_projects` | Lists all projects & workspaces in your Reeling account. |
| `reeling_list_channels` | Lists all connected channels across all 15 networks with handle names and account status. |
| `reeling_get_channel_options` | Retrieves publishing options for a connected channel, such as Pinterest boards (ID, name, privacy) or TikTok creator options. |
| `reeling_publish_post` | Publishes 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_status` | Checks delivery, processing, and publishing status for a specific post. |
| `reeling_discover_community_questions` | Discovers high-intent daily questions on Reddit and Quora matching your topics and returns remaining daily/weekly cadence quota. |
| `reeling_draft_community_answer` | Generates a value-first, non-promotional answer for a Reddit or Quora thread and evaluates its 0–100 Pre-Publish Spam & Shadowban score. |
| `reeling_get_analytics` | Fetches aggregated analytics: total views, likes, comments, impressions, and per-platform breakdown. |
| `reeling_sync_metrics` | Triggers a live sync against YouTube, Bluesky, Instagram, Threads, and TikTok APIs. |
| `reeling_evaluate_content_jev` | Evaluates video scripts and captions using Reeling's JEV hook and retention diagnostics. |
| `reeling_get_inbox` | Retrieves audience comments across social channels into a unified inbox. |
| `reeling_reply_to_comment` | Posts a direct reply to a comment on any connected social platform. |
| `reeling_adapt_content_ai` | Uses Reeling's AI copy engine to adapt a hook/script for TikTok, Instagram, YouTube, Threads, or Bluesky. |
| `reeling_generate_video` | Requests short-form video generation through Reeling’s configured service; plan allowance and provider processing apply. |
| `reeling_create_storyboard` | Generates structured multi-scene storyboards (30s up to 5 minutes) broken into consecutive 5s cinematic cuts with audio/foley cues. |
| `reeling_stitch_storyboard` | Requests scene rendering and stitching through Reeling’s configured video workflow. |

---

## 🔑 Getting Started

1. **Obtain your API Key**:
   - Go to [reeling.app](https://reeling.app) and sign in.
   - Navigate to **Settings** → **API Keys**.
   - Generate a new key (starts with `rl_...`).

2. **Run the server**:

   ```bash
   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](https://mcp.reeling.app/install).

---

## 💻 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`

```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:
```json
{
  "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:

```json
{
  "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:

```json
{
  "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:

```bash
# 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](https://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](https://reeling.app/developers). 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:

```bash
npx @modelcontextprotocol/inspector node bin/cli.js
```

Or test SSE mode:
```bash
node bin/cli.js --sse --port 3005
curl http://localhost:3005/health
```

---

## 📄 License
MIT © [reeling.app](https://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](SECURITY.md) before reporting a vulnerability.

## Working examples

Clone [reeling-examples](https://github.com/yomariano/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](https://reeling.app/developers/examples).

## Architecture

```mermaid
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

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

See [CONTRIBUTING.md](CONTRIBUTING.md), [CHANGELOG.md](CHANGELOG.md), and [GitHub releases](https://github.com/yomariano/reeling-mcp/releases). Installs above use a versioned GitHub tag; npm publication requires a separate authenticated npm release.

## Setup guide preview

![Reeling MCP setup guide with transport choices and configuration instructions](docs/mcp-setup.png)

Local preview of the public developer guide. [Open the current setup guide](https://reeling.app/developers/mcp).

TDQS

A3.5/5.0

Scored across 18 tools

Disambiguation5/5

Each tool targets a distinct action or resource within the social media workflow. While several tools involve content creation (adapt_content_ai, draft_community_answer, generate_video, create_storyboard), their descriptions clearly differentiate the target platforms and output types, preventing confusion.

Naming Consistency5/5

All tools are prefixed with 'reeling_' and use snake_case with a consistent verb_noun structure (e.g., reeling_get_platform_matrix, reeling_publish_post). The only variation is the inclusion of acronyms like JEV, but the pattern remains predictable.

Tool Count4/5

18 tools is slightly above the ideal 3-15 range but is justified by the breadth of functionality (discovery, creation, publishing, analytics, engagement). No obvious redundant tools, though the set could be trimmed if some advanced features are rarely used.

Completeness4/5

Coverage is strong across the core lifecycle: platform discovery, content creation, publishing, analytics, and engagement. Minor gaps exist, such as no tools for updating/deleting posts or managing projects/channels beyond listing, but these are likely handled via the web interface and do not block core agent workflows.

Maintenance

ActivityActive
ResponsivenessLimited data