Reeling MCP server setup

Choose local or hosted transport

The open-source adapter runs locally over stdio with Node.js 22 or later. The hosted endpoint uses Streamable HTTP at https://mcp.reeling.app/mcp. Legacy SSE remains available at /sse for existing clients. Choose the transport your installed client supports; URL and header configuration differs between clients.

The source is installable from a versioned GitHub tag. The unscoped npm package name reeling-mcp is not currently published, so use the exact GitHub command below.

• Open-source adapter and releases
• Hosted installation reference

Configure the local adapter

Use this command-and-arguments shape in Claude Desktop or Cursor’s supported MCP configuration. Replace YOUR_API_KEY only in your local secret configuration. Never commit a real key or paste it into chat. Reload the client connection after saving.

The GitHub tag pins the adapter source. Review the release and dependency lockfile before installing it. If npx is unavailable to a desktop client, install Node.js and use its absolute executable path.

{
  "mcpServers": {
    "reeling": {
      "command": "npx",
      "args": [
        "-y",
        "github:yomariano/reeling-mcp#v1.0.1"
      ],
      "env": {
        "REELING_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

• Generate a configuration template
• Cursor MCP configuration

Check projects and channels first

Create a project and connect its destinations in Reeling. Create an API key under Settings, then allow reeling_list_projects and reeling_list_channels. Select the exact project instead of choosing the first item from a multi-project account.

Channel capabilities describe the server’s configured integration, not proof of a successful post or approval for every visibility setting. Consult the platform requirements and inspect channel options before enabling a write.

• API authentication and account reads
• Current platform requirements

Approve consequential tools deliberately

Publishing, replies, metric synchronization and AI generation can change external state or consume a plan allowance. Keep client-side tool approval enabled and review the destination, content, schedule and visibility. A Reeling API key is not a read-only credential.

The MCP publish tool exposes a subset of the REST options. When your workflow needs an exact channel ID or a platform-specific setting absent from the tool schema, use the reviewed REST example rather than assuming the adapter forwards it.

• Request-draft and status-polling examples

Recover from setup errors

A connection error can come from a missing Node executable, a client using a different PATH, unsupported transport or malformed JSON. Confirm that tools/list works before investigating account permissions.

For authentication and authorization errors, check the API key, current plan, project ownership and channel permissions. Do not assume every 403 requires payment. Preserve an existing post ID after an ambiguous publish timeout and check its status before retrying.

• Reeling plans
• MCP architecture documentation