Instagram Mcp
Let your coding agent publish posts, reels, stories, and DMs and pull Instagram analytics from one MCP server instead of clicking through Meta’s dashboards.
Overview
io.github.mcpware/instagram-mcp is an MCP server for the Grow phase that exposes 23 Instagram Graph API tools so agents can publish content, manage DMs, and read analytics.
What is this MCP server?
- 23 MCP tools covering Instagram Graph API: posts, stories, reels, DMs, and analytics
- stdio npm package @mcpware/instagram-mcp (v1.0.4) with required Meta long-lived token and business account ID
- Configurable INSTAGRAM_API_VERSION (default v19.0) for Graph API compatibility
- Business-account requirement—personal-only profiles are out of scope
- Agent-driven publishing and inbox workflows without custom Meta API glue code
- 23 MCP tools documented for Instagram Graph API coverage
- Server version 1.0.4; npm package @mcpware/instagram-mcp
- Required env: INSTAGRAM_ACCESS_TOKEN, INSTAGRAM_ACCOUNT_ID
What problem does it solve?
Solo builders waste hours in Meta Business Suite or brittle scripts when they want agents to post, reply, or report on Instagram.
Who is it for?
Indie founders with an Instagram Business account who already use MCP and want agent-driven publishing plus basic analytics.
Skip if: Personal Instagram accounts, teams that need full ad-buying workflows, or builders who cannot store a long-lived Meta secret locally.
What do I get? / Deliverables
After you register the server with a valid business token and account ID, your agent can call Graph API operations for posts, stories, reels, DMs, and analytics from the IDE.
- Agent-callable publish and manage operations for posts, stories, and reels
- DM and messaging actions exposed as MCP tools where Graph API allows
- Analytics reads aligned with included Graph API tool surface
Recommended MCP Servers
Journey fit
Instagram is where solo builders compound attention after launch; canonical shelf is Grow because ongoing posting and engagement are the main loop, not one-time validation. Content is the right subphase because the 23 tools center on creating and managing feed media, stories, reels, and messaging—not infra or error triage.
How it compares
MCP Graph API integration with 23 tools, not a social copywriting or growth strategy skill.
Common Questions / FAQ
Who is io.github.mcpware/instagram-mcp for?
Solo builders and small teams with a Meta-connected Instagram Business account who want their AI coding agent to run feed, story, reel, DM, and analytics actions via MCP.
When should I use io.github.mcpware/instagram-mcp?
Use it in Grow when you are maintaining Instagram as a channel—scheduling content, responding in DMs, or pulling metrics—while building or operating the rest of the product in other tools.
How do I add io.github.mcpware/instagram-mcp to my agent?
Install @mcpware/instagram-mcp from npm, set INSTAGRAM_ACCESS_TOKEN and INSTAGRAM_ACCOUNT_ID (and optional INSTAGRAM_API_VERSION), add the stdio server entry in Claude Code or Cursor MCP config, then invoke tools from chat.