Ig MCP Server

A Model Context Protocol (MCP) server that provides seamless integration with Instagram's Graph API, enabling AI applications to interact with Instagram Business accounts programmatically. That is what the ig mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 6 tools. What each one is for:

• instagram_basic — instagram_content_publish
• instagram_manage_insights — instagram_manage_comments
• pages_show_list — pages_read_engagement
• pages_manage_metadata — pages_read_user_content
• instagram_manage_messages — Required for Direct Messaging features
• Contributing — 1. Fork the repository 2. Create a feature branch (git checkout -b feature/amazing-feature) 3. Commit your changes (git commit -m 'Add amazing

What it needs from you

Configuration is passed through the environment: INSTAGRAM_ACCESS_TOKEN, FACEBOOK_APP_ID, FACEBOOK_APP_SECRET, INSTAGRAM_BUSINESS_ACCOUNT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

1. Instagram Business Account: Must be connected to a Facebook Page 2. Facebook Developer Account: Required for API access 3. Access Token: Long-lived access token with appropriate permissions 4. Python 3.10+: For running the MCP server (required by MCP dependencies)

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ig MCP's toolset — instagram_basic, instagram_manage_insights, pages_show_list and 3 more — is a fair guide to whether it matches your workflow. It is maintained by jlbadano; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.