Connect Cursor to ReelDrop

1. 1

   Step 1: Add the server to mcp.json

   Open Customize → MCPs in the sidebar and open the MCP config, or edit the file directly. ~/.cursor/mcp.json makes ReelDrop available in every project; .cursor/mcp.json inside a project limits it to that project, and wins if both name the same server.

   ~/.cursor/mcp.json

   Copy

   {
     "mcpServers": {
       "reeldrop": {
         "url": "https://mcp.reeldrop.io/mcp"
       }
     }
   }

2. 2

   Step 2: Sign in with your ReelDrop account

   Save the file. Cursor finds that the server needs a sign-in and offers to connect next to reeldrop in the MCPs list. Click it, log in to ReelDrop in the browser window that opens and approve. Cursor registers itself automatically, so leave out any auth block in the config.

   If nothing changes after saving, restart Cursor.

3. 3

   Step 3: Check the tools loaded

   reeldrop lists its tools under Available Tools in the MCPs list, and they appear in the tools list at the top of the agent chat. If it stays disconnected, open the Output panel and choose MCP Logs.

4. 4

   Step 4: 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.

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.