Instagram MCP Server

Created By
jlbadanoa year ago
A production-ready Model Context Protocol (MCP) server that enables AI applications to seamlessly interact with Instagram Business accounts.
Overview

What is Instagram MCP Server?

Instagram MCP Server is a production-ready Model Context Protocol (MCP) server that allows AI applications to interact seamlessly with Instagram Business accounts through the Instagram Graph API.

How to use Instagram MCP Server?

To use the Instagram MCP Server, set up an Instagram Business account, create a Facebook app, obtain the necessary API credentials, and run the server with Python. You can then make API calls to manage Instagram accounts and media.

Key features of Instagram MCP Server?

  • Retrieve Instagram business profile details
  • Fetch recent media posts and engagement metrics
  • Publish images/videos to Instagram
  • Analyze post performance and generate content strategies

Use cases of Instagram MCP Server?

  1. Automating social media management for businesses.
  2. Analyzing engagement metrics for marketing strategies.
  3. Publishing content programmatically to enhance user engagement.

FAQ from Instagram MCP Server?

  • What do I need to use the Instagram MCP Server?

You need an Instagram Business account, a Facebook Developer account, and a long-lived access token with the required permissions.

  • Is there a limit on API calls?

Yes, the server implements rate limiting to comply with Instagram's API limits, such as 200 calls per hour for profile requests.

  • Can I use this server for personal Instagram accounts?

No, the server is designed specifically for Instagram Business accounts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jlbadano
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago