Skip to main content
Glama
Sign In

Instagram MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Instagram MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/instagram-mcp-server
GitHub Stars
1
Server Listing
Instagram MCP Server
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are nearly indistinguishable: both are described as "Step 3 (FINAL) of workflow" and both require the same query_contexts prerequisites plus "construct the body from steps 1-2." Only prompts_menu is clearly distinct, so an agent must guess whether to read data or perform a write through two nearly identical entry points.

Naming Consistency4/5

execute_action, query_data, and query_contexts follow a clean verb_noun snake_case convention. prompts_menu breaks the pattern (noun_noun) and is a minor deviation, but the overall scheme remains readable.

Tool Count3/5

Four outward tools is thin for an entire Instagram platform, and it is achieved by collapsing many operations behind polymorphic request parameters (prompts_menu alone exposes 4 operations). The small count hides a large, hard-to-discover surface rather than genuinely scoping it.

Completeness3/5

The dispatch pattern (contexts → details → query/execute) plus prompt access covers the core read/write lifecycle and is self-consistent. However, there is no direct way to inspect results or action status, and all actual capabilities are invisible until runtime introspection, leaving notable gaps.

Available Tools

4 tools
execute_actionInstagram Execute ActionA
Destructive
Inspect

Execute Instagram action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, account_id AND available_actions

  2. request='actions_details' with actions=['xxxx'] - Get detailed body structure for specific action(s)

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuInstagram PromptsA
Read-only
Inspect

Access Instagram prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for Instagram

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsInstagram Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Instagram data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, account_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['table_a', 'table_b'] – REQUIRED before querying. Returns the exact request body, required identifiers, fields, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataInstagram Data QueryB
Read-only
Inspect

Query Instagram data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, account_id AND available_actions

  2. request='actions_details' with actions=['xxxx'] - Get detailed body structure for specific action(s)

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • Instagram MCP Server

      aayushjain1811
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Remote MCP Server that gives Claude direct, tool-based access to your Instagram Business account through the Meta Graph API — profile data, posts, comments, publishing, insights, analytics, hashtags, messaging, and real-time webhooks.
      7 npm
      MIT

    • Instagram MCP Server

      mbay-ODW
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.
      MIT

    • Instagram MCP Server

      abdulsammad-lgtm
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for interacting with Instagram/Meta APIs, enabling AI agents to manage content, analyze performance, research competitors, and handle publishing workflows.
      -
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources