MCP server

Reelspan runs a hosted Model Context Protocol server. Add it to an AI client once and the agent can publish videos, photos and text, schedule posts, write captions and read results, using the same API key, scopes and limits as the REST API. There is nothing to install.

Before you start

1. Create an API key in the dashboard under Developers → API keys. Tick Test key to try things first: a test key (rs_test_…) runs every check but never posts to a network.
2. Keep it in an environment variable, for example REELSPAN_API_KEY, rather than pasting it into shared files.

Connect a client

Claude Code

claude mcp add --transport http reelspan https://api.reelspan.com/mcp \
  --header "Authorization: Bearer $REELSPAN_API_KEY"

Run /mcp inside Claude Code to check that it connected. Add --scope project to save it in the project's .mcp.json for your team; that file can read the key from the environment:

{
  "mcpServers": {
    "reelspan": {
      "type": "http",
      "url": "https://api.reelspan.com/mcp",
      "headers": { "Authorization": "Bearer ${REELSPAN_API_KEY}" }
    }
  }
}

Claude (desktop and web)

1. Open Customize → Connectors, select + Add, then Add custom connector.
2. Name it Reelspan and enter https://api.reelspan.com/mcp as the server URL.
3. Under Authentication, choose No sign in.
4. Under Request headers, add Authorization with the value Bearer rs_live_… (your key).
5. Select Add, then turn the connector on in a chat.

On Team and Enterprise plans an owner adds the connector under Organization settings → Connectors, and everyone who uses it shares that one key, so give it only the scopes they need.

Cursor

Add the server to .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "reelspan": {
      "url": "https://api.reelspan.com/mcp",
      "headers": { "Authorization": "Bearer ${env:REELSPAN_API_KEY}" }
    }
  }
}

VS Code

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

{
  "inputs": [
    { "type": "promptString", "id": "reelspan-key", "description": "Reelspan API key", "password": true }
  ],
  "servers": {
    "reelspan": {
      "type": "http",
      "url": "https://api.reelspan.com/mcp",
      "headers": { "Authorization": "Bearer ${input:reelspan-key}" }
    }
  }
}

ChatGPT

ChatGPT signs in with your Reelspan account instead of an API key. It needs a plan that can add custom MCP servers (Plus or Pro, or a Business, Enterprise or Edu workspace where the admin allows it).

1. Open chatgpt.com/plugins, select +, then Add custom MCP server.
2. Name it Reelspan. Under Connection, choose Server URL and enter https://app.reelspan.com/mcp.
3. Set Authentication to OAuth and leave the client ID and secret empty: ChatGPT registers itself.
4. Confirm, then sign in to Reelspan when ChatGPT opens it, check the workspace, and select Allow.

In a chat, type @ and pick Reelspan, then ask in plain words. ChatGPT asks before each tool that changes something. If your account still has the older menu, the same setup is under Settings → Apps & Connectors → Advanced settings → Developer mode.

The sign-in flow uses https://app.reelspan.com/mcp. Clients that send an API key use https://api.reelspan.com/mcp. Both reach the same tools.

Any other client

Any client that supports remote Streamable HTTP servers works. Most take a config like Cursor's above: the URL plus an Authorization header. If your client can't send headers, put the key in the path instead:

https://api.reelspan.com/mcp/rs_live_your_key

Treat that URL like the key itself: anyone who sees it can use your account. Prefer the header wherever you can.

To use Reelspan from code, see the agent framework guides, starting with LangChain.

Tools

Every tool calls the REST API with your key, so the key's scopes decide what the agent can do. Media is passed as public https URLs (Google Drive and Dropbox share links work); the MCP tools don't take local files.

Account and profiles

Network settings

Publishing

Live posts

Scheduling and approvals

Media library

Captions

Analytics

Webhooks

How publishing works

The publish tools run in the background: they return a request_id straight away, and the agent calls upload_status to see each network's result. upload_video takes wait: true to wait up to a minute for the results instead. Per-network settings go in the tool's options object, using the same field names as the REST API, for example {"youtube_title": "…", "privacy_level": "SELF_ONLY"}. Each network's fields are on its page under Networks.

Authentication

• API key in the header (Authorization: Bearer <key>) at https://api.reelspan.com/mcp. Live keys start with rs_live_, test keys with rs_test_.
• API key in the path (/mcp/<key>) for clients that can't send headers.
• OAuth sign-in at https://app.reelspan.com/mcp for clients that support it, such as ChatGPT. The token acts for the workspace you chose, with every scope.

Ten failed key attempts from one IP address lock that address out for 5 minutes, the same as the REST API. See Authentication.

Safety

• Start with a test key. Posts made with an rs_test_ key go through every check and show as done, but nothing reaches the networks and nothing counts against your plan (up to 500 test posts a day). See Test mode.
• Use the sandbox network to watch the whole flow without a connected account: it accepts video, photo and text posts and needs no connection.
• Give the agent only the scopes it needs. A key with just Read can check status and history but can't publish. A key without Profiles can't create or delete profiles.
• Review destructive actions. delete_profile, cancel_scheduled and unpublish_post are marked as destructive, and clients that honour the marking ask before running them.
• One key per agent or customer, so you can revoke one without touching the others.

Example prompts

• "List my profiles and which networks each one has connected."
• "Post this video to TikTok, YouTube and Instagram for my-brand tomorrow at 9am London time, with a caption that fits each network."
• "Post 'Testing Reelspan' as a text post to the sandbox network for my-brand, then check the status."
• "How did yesterday's post do on each network?"