Instagram Mcp Server

What is Instagram MCP Server?

An MCP server that allows you to control your Instagram account from Claude — post, analyze, reply to DMs, manage comments — all by chatting. It uses the Instagram Login API (graph.instagram.com) and requires an Instagram Business or Creator account.

How to use Instagram MCP Server?

Deploy the server (free on Render) or run locally with Python 3.11+. Connect to Claude via web or desktop. Provide a META_ACCESS_TOKEN and IG_USER_ID. Then ask Claude in plain English to perform Instagram actions.

Key features of Instagram MCP Server

• 24+ tools covering account info, insights, publishing, comments, engagement, DMs, hashtags, events, and ads
• Publish photos, reels, and carousel posts with captions and hashtags
• Read, reply to, hide, and delete comments; like posts and comments
• Send DMs within the 24-hour window or 7-day Human Agent window
• Get account and media insights (reach, saves, views, etc.)
• Support multiple Instagram accounts by running separate server instances

Use cases of Instagram MCP Server

• Content creators: get morning briefings, compare reel performance, draft captions
• Professionals: reply to comments professionally, track follower growth, audit content
• Small businesses: handle customer DMs, publish product photos, analyze best post types

FAQ from Instagram MCP Server

What kind of Instagram account is required?

You need an Instagram Business or Creator account. It cannot be a personal account.

How do I get an access token?

Create a Meta Developer app, add the "Manage messaging & content on Instagram" use case, then generate a META_ACCESS_TOKEN and get your IG_USER_ID from the Meta dashboard.

Where does my data live?

The server communicates directly with Meta's Instagram Graph API. It does not store your data locally except for environment variables.

What are the maximum video length and file requirements?

Videos must be ≤90 seconds, use a supported codec, and be hosted at a public HTTPS URL (e.g., Cloudinary, S3, GitHub raw). Local file paths won't work.

What transport and authentication does the server use?

It runs as an MCP server using FastMCP 3.x with streamable-http (for web) or stdio (for desktop). Authentication is via a long-lived META_ACCESS_TOKEN that needs refreshing every 60 days.