INSSIST MCP server

@inssist/mcp

The MCP server that lets an AI agent work inside your own logged-in Instagram session, through the INSSIST Chrome extension.

Every other Instagram MCP wraps the Graph API: business accounts only, no Stories, no music, no DMs, only what Meta chooses to expose. This one drives the browser you are already signed into, so Claude Code, Codex, Cursor or Claude Desktop can read profiles and DMs, publish and schedule posts, reels and stories with music, pull insights and audience reports, and download media, on a personal, creator or business account alike.

Nothing is proxied through a cloud and no Instagram credentials are ever held: the server hands each tool call to the extension over loopback, and the extension answers from the browser.

Claude Code / Codex / Cursor / Claude Desktop
  │  stdio (MCP)
  ▼
@inssist/mcp                    ← this package, runs on your machine
  │  ws://127.0.0.1:48231
  ▼
INSSIST extension (Chrome)
  │
  ▼
Instagram, in your own session

Requirements

• Chrome (or another Chromium browser) with INSSIST installed and Instagram open and logged in.
• Node.js 22 or newer (npx comes with it).
• An MCP client. Any harness that can launch a stdio server works.

Install

Register the server with your agent. It downloads and starts the server by itself; there is nothing to run by hand.

Claude Code

claude mcp add inssist -- npx -y @inssist/mcp

Codex

codex mcp add inssist -- npx -y @inssist/mcp

Claude Desktop, including Cowork: download inssist-mcp.mcpb and double-click it. One step, runs on Claude's built-in Node.js, no terminal needed.

Cursor, Windsurf, Gemini CLI and any other client: add this to its MCP config (Cursor: .cursor/mcp.json):

{ "mcpServers": { "inssist": { "command": "npx", "args": ["-y", "@inssist/mcp"] } } }

Connect the browser

1. In Chrome, open instagram.com and click the INSSIST menu.
2. Click Connect to AI Agents and turn the toggle on.
3. The panel shows Connected within a few seconds.

Pairing is automatic: the toggle is the consent. The extension dials the server, both sides store a token for silent reconnects, and turning the toggle off disconnects and stops all retries. Several Chrome profiles can connect to the same server; each shows up as an instance in account_info.

Several agents at once are fine too. Each harness starts its own @inssist/mcp process; the first one to bind the port becomes the hub, later ones join it as peers and relay through it, so Claude Code in two terminals, Claude Desktop and Cursor all share the same browsers. When the hub's harness closes, one of the peers takes the port over and the extension reconnects to it.

Try it

Who am I logged in as, and how many followers do I have?
Show me the last 5 posts from @nasa with their like counts.
List my unread DMs and draft a reply to the first one. Don't send it yet.
Schedule /Users/me/reel.mp4 as a reel for tomorrow 9am with a caption about spring, and add a trending track.
Run an unfollowers scan and tell me who left this week.
Download the last 20 posts from @natgeo to my machine.

Tools

Shortened. The full README is on GitHub.