OpenInstaFlow — Instagram MCP server

An MCP server that exposes the Instagram Graph API to any MCP client (Claude Desktop, Claude Code, Cursor, …). Bring your own Meta token — point the server at your Instagram Business/Creator account and the model can read your profile, posts and insights, publish media, manage Facebook Pages, and handle DMs.

Runs as a stdio subprocess — no server to host. Just npx openinstaflow.

Features

🔧 Tools (model-controlled)

📊 Resources (application-controlled) — live, attachable context: instagram://profile, instagram://media, instagram://insights.

💬 Prompts (user-controlled) — ready-made templates: analyze_engagement, content_strategy, hashtag_analysis.

Quick start

Add it to your MCP client config (Claude Desktop: claude_desktop_config.json; Claude Code: .mcp.json):

{
  "mcpServers": {
    "openinstaflow": {
      "command": "npx",
      "args": ["-y", "openinstaflow"],
      "env": {
        "IG_ACCESS_TOKEN": "",
        "IG_USER_ID": "",
        "IG_LOGIN_KIND": "ig_login"
      }
    }
  }
}

Restart the client and the OpenInstaFlow tools/resources/prompts appear.

Authentication

Set these in the server’s env block (above):

Every tool also accepts optional access_token / ig_user_id arguments that override the env for that single call — so one running server can drive multiple accounts.

Permissions

• Reading + publishing need a Business/Creator account and the usual content-publishing permissions (instagram_basic, instagram_content_publish, instagram_manage_insights).
• DM tools (get_conversations, get_conversation_messages, send_dm) need Advanced Access with instagram_manage_messages, and (for FB Login) a Page token. Without it, Instagram returns a clear permission error.

Media must be a public URL

Instagram fetches media server-side, so publish_media takes public HTTPS URLs (image_url / video_url / carousel item urls) — not local files. Host the media somewhere publicly reachable first.

Development

npm install        # installs deps (+ builds via the prepare hook)
npm run build      # tsc → dist/
node verify.mjs    # MCP handshake harness: lists tools/resources/prompts (+ live call if IG_ACCESS_TOKEN is set)

Inspect interactively with the official inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Out of scope (for now)

• Webhooks / real-time push (incoming comments, mention/DM notifications) — needs a public HTTPS callback, which a stdio subprocess can’t provide. (The DM tools here are request/response.)
• Shopping / product tagging — needs a Commerce catalog + review.

License

MIT