Instagram MCP

What drashrafsaiyed-cyber/instagram-mcp MCP server does

drashrafsaiyed-cyber/instagram-mcp MCP server gives Claude access to an Instagram Business or Creator account through the Instagram Login API. It can retrieve account details, recent media, account-level insights, and per-post metrics such as reach, views, saves, and interactions.

The server also covers content operations. Claude can publish photos, reels, and carousels, update the profile bio or website, delete posts, search public hashtag posts, and interact with media by liking or unliking it. Comment tools support reading, replying, liking, hiding, and deleting comments.

Messaging capabilities include listing conversations, reading thread messages, and sending replies through the standard 24-hour window or the documented 7-day Human Agent window. The repository also lists tools for creating and listing events, discovering linked ad accounts, and reading advertising metrics such as spend, reach, and click-through rate.

How it works

The server sits between an MCP client and graph.instagram.com. Claude sends tool calls over MCP, while the Python server makes HTTPS REST requests to Instagram's API v21.0 using the configured access token and Instagram user ID. FastMCP 3.x supports both local stdio operation and streamable HTTP operation.

For web or mobile Claude usage, the project can be deployed to Render and connected through an /mcp endpoint. For local Claude Desktop usage, the repository is run with uv and registered as an MCP server. Multiple Instagram accounts can be exposed by running the same project with separate environment values and separate client entries.

Setup and configuration

To run drashrafsaiyed-cyber/instagram-mcp MCP server, use Python 3.11 or later, an Instagram Business or Creator account, and a Meta developer app configured with the “Manage messaging & content on Instagram” use case. The required credentials are META_ACCESS_TOKEN and IG_USER_ID; ACCOUNT_NAME can label an account when several configurations are present.

The access token is generated through Meta's Instagram Login setup. Tokens expire and should be refreshed before their stated lifetime, which the repository documents as 60 days. The account must also be added as a tester in the Meta app when using that development setup.

A local setup clones the repository, runs uv sync, creates .env from .env.example, fills in the credentials, and starts uv run server.py. A Render deployment requires entering the token and user ID during deployment, then adding the resulting MCP URL to Claude's integrations.

Tools and capabilities

The listed operations include:

• Account information, profile updates, recent media, and account or media insights.
• Photo, reel, and two-to-ten-image carousel publishing.
• Comment retrieval, replies, likes, hiding, and permanent deletion.
• Media likes and unlikes, post deletion, and hashtag search.
• Conversation listing, message retrieval, and eligible DM replies.
• Event creation and listing, plus ad account and ad performance queries.

Limitations and notes

Instagram fetches media from its source URL, so photos and videos must be hosted at publicly reachable HTTPS URLs. Local filesystem paths do not work for publishing. Video processing can fail when a video is longer than 90 seconds, uses an unsupported codec, or becomes unavailable after Instagram first fetches it.

DM results can be empty when there is no active 24-hour messaging window. Insights errors may result from using a metric that is valid for an account endpoint but not a media endpoint. An expired or incorrect token must be regenerated or refreshed. Claude Desktop may need a full restart before newly registered tools appear.

The repository is released under the MIT license. It is intended for Instagram accounts supported by the Instagram Login API and does not describe support for ordinary personal accounts.