MCP · CURSOR

Instagram MCP for Cursor

Build against real Instagram data without leaving Cursor. The agent calls the API, reads the response, writes the code.

One-click install (coming soon).

Coming to this page. Until then, use mcp.json below.

Manual: mcp.json.

Add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Get the key from API keys. Then open Cursor Settings → MCP and confirm instadata shows green.

{
  "mcpServers": {
    "instadata": {
      "url": "https://mcp.instadata.dev",
      "headers": {
        "Authorization": "Bearer ik_live_..."
      }
    }
  }
}

In a shared repo, keep the key out of git. Use the per-user global config, or an env var if your setup supports it.

Why this is useful in an editor.

Types"Call get_profile for @nasa and generate a TypeScript type for the response."
The same recordThe agent sees the same record the REST API returns, so generated code matches production.
Request idsEvery call has a request id in the dashboard logs.
Pipelines"Fetch the last 20 reels for this handle, transcribe them, and write a script that stores them in Postgres."

Then go REST.

Same endpoints, same record.

curl "https://api.instadata.dev/v1/instagram/channel-stats?handle=nasa" \
  -H "Authorization: Bearer ik_live_..."

Cost.

$5 per 1,000 credits. 25 free credits on signup, no card. list_endpoints is free. Failed calls are free. Pricing

Questions.

Does Cursor's agent spend credits automatically?

Only when it calls a tool. Cursor asks before running tools unless you enable auto-run.

Project or global config?

Global for your key. Project config if the team shares a server entry without secrets.

Works in Windsurf / VS Code too?

Yes. The same remote server is documented on the MCP server docs.

MCP server · MCP docs · Endpoints · Claude