Docs menuAI assistants (MCP)

Setup guide · AI assistants (MCP)

Connect Claude to ReelDrop

Add ReelDrop's server URL to Claude as a custom connector, or with one command in Claude Code, and sign in with your ReelDrop account when the browser opens. There is no API key. It takes about two minutes, and the same connector works in Claude Desktop and on claude.ai.

About two minutesNo API keyOAuth with your ReelDrop accountUpdated

On this page
  1. Before you start
  2. 1. Copy the server URL
  3. 2. Add it in Claude Desktop or claude.ai
  4. 3. Or add it in Claude Code
  5. 4. Sign in when the browser opens
  6. 5. Run the first-run checklist
  7. If it asks for an API key
  8. Disconnect
  9. Other MCP clients
  10. FAQ
  11. Related
  12. Sources

Before you start

  • A ReelDrop account on any plan. MCP access is included on the free Starter plan too.
  • A ReelDrop workspace with an Instagram account connected, if you want the assistant to actually schedule and read analytics.
  • Claude on any plan. Free accounts can add one custom connector; Pro, Max, Team and Enterprise can add more. On Team and Enterprise an owner adds the connector for the organisation and members click Connect.
  1. Step 1: Copy the server URL

    In ReelDrop, open the Connect your AI assistant page. It shows the server URL with a copy button and setup tabs for each client. The URL is the same for everyone:

    Server URL

    https://mcp.reeldrop.io/mcp
  2. Step 2: Add it in Claude Desktop or claude.ai

    Open Customize → Connectors, click + Add, then Add custom connector. Name it ReelDrop, paste the URL and click Continue. Leave authentication on sign in and the OAuth client on Claude’s published identity, which is the recommended option; ReelDrop accepts it, and it also accepts Register automatically.

    A connector added on claude.ai shows up in Claude Desktop too, and the other way round.

  3. Step 3: Or add it in Claude Code

    It is one terminal command. Add -s user before the name to make it available in every project rather than only the current one.

    terminal

    claude mcp add --transport http reeldrop https://mcp.reeldrop.io/mcp
  4. Step 4: Sign in when the browser opens

    Your browser opens ReelDrop's sign-in page. Log in with your normal ReelDrop account and approve the connection. This is standard OAuth: Claude gets a token scoped to your account, and your password never passes through it.

    In Claude Code, run /mcp, pick reeldrop and choose to authenticate if the browser does not open on its own.

  5. Step 5: Run the first-run checklist

    Ask these four things in a new chat. All of them only read, so nothing changes on your account, and each answer proves a different part of the connection works:

    • "List my ReelDrop workspaces." Your real workspace names come back, not a guess.
    • "Which Instagram account is connected to that workspace, and is the connection healthy?"
    • "How much of my plan have I used this month?" On the free Starter plan, this is where the upgrade reply shows up instead.
    • "When is my next open posting slot?" If no posting schedule is saved yet, it asks for your timezone once and saves it to the workspace.

If it asks for an API key

Claude should never ask you for an API key, a client ID or a bearer token for ReelDrop. If it does, it is pointed at the wrong address: check that the URL is exactly https://mcp.reeldrop.io/mcp, with /mcp on the end. The only client that uses a token is Meta Muse, because it has no browser to sign in with.

Disconnect

On claude.ai or in Claude Desktop, open Customize → Connectors and remove ReelDrop. In Claude Code, run claude mcp remove reeldrop, which also deletes its stored sign-in, or clear the sign-in from /mcp. Reconnecting always means approving the sign-in in the browser again, and posts already scheduled keep publishing either way.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth connects the same way: point it at the URL above and complete the sign-in when the browser opens. ReelDrop supports both automatic client registration and client ID metadata documents, so there is nothing to create on the ReelDrop side first. ChatGPT, Cursor, VS Code, Windsurf and Gemini each have their own guide.

ReelDrop is also listed on Smithery and in the official MCP registry as io.reeldrop/reeldrop, so clients that browse either can find the server without you pasting the URL.

Frequently asked questions

Do I need an API key?

No. Sign-in is OAuth with your ReelDrop account; if Claude asks you for an API key, it is not pointed at the right URL. The one client that does take a token is Meta Muse, which cannot open a browser to sign in. See Connect Meta Muse to ReelDrop.

Can I connect more than one assistant?

Yes. Each client signs in separately, and each one acts as your ReelDrop account.

Claude says the connection expired. What now?

Reconnect from Customize → Connectors and sign in again. ReelDrop issues Claude a 30-day token and renews your session behind it, so this should be rare.

I'm on the free plan. What happens if I connect?

Everything works, within the free plan’s limits. MCP access is on every plan, and the tools follow the same limits as the app, so a feature the free plan leaves out, such as replying from the inbox, still answers that it is not included.

Sources

Something here out of date or missing a step? Tell us and we will fix it.

Ready to connect? It takes two minutes.

Grab the server URL from the connect page and paste it into your assistant. Sign in once and you are done.

Built in Toronto by Piyush Sachdeva.

© 2026 10517933 Canada Ltd. (operating as reeldrop.io). All rights reserved. Canadian-owned and operated
Not affiliated with Instagram or Meta Platforms. Built by Piyush