Meta MCP

What mikusnuz/meta-mcp MCP server does

mikusnuz/meta-mcp MCP server connects an MCP-compatible AI client to Instagram Graph API, Threads API, and selected Meta platform management operations. The repository README describes support for Graph API v26.0, while the supplied listing references v25.0; check the project version before relying on a specific API revision.

The server covers content publishing, account and post analytics, comments, replies, hashtag lookup, collaboration invites, and Instagram direct-message operations. Threads capabilities include text and media publishing, carousels, polls, GIFs, topic tags, link attachments, reply controls, post search, insights, deletion, locations, mentions, oEmbed, and profile discovery. Meta-level tools handle access-token exchange, refresh, inspection, app information, and webhook subscriptions.

How it works

The server communicates over MCP and uses environment variables to select the Instagram, Threads, and Meta credentials available to the process. Publishing media uses the platform APIs: Instagram video operations wait for processing, and carousel publishing accepts between two and ten items. Instagram media generally needs a publicly accessible HTTPS URL.

Some operations have platform constraints. Hashtag searches are limited to 30 unique hashtags in a rolling seven-day period. Instagram accounts must be professional Business or Creator accounts; personal accounts cannot use the Instagram Graph API. Threads accounts do not require an Instagram account link according to the README.

Setup and configuration

The documented npm configuration runs the package with npx:

{
  "mcpServers": {
    "meta": {
      "command": "npx",
      "args": ["-y", "@mikusnuz/meta-mcp"]
    }
  }
}

Set only the variables for the platforms and operations you use. Instagram publishing and account tools use INSTAGRAM_ACCESS_TOKEN and INSTAGRAM_USER_ID. Instagram messaging additionally uses INSTAGRAM_MESSAGING_ACCESS_TOKEN and INSTAGRAM_PAGE_ID. Threads tools use THREADS_ACCESS_TOKEN and THREADS_USER_ID. Token and webhook management requires META_APP_ID and META_APP_SECRET for the applicable operations.

mikusnuz/meta-mcp MCP server can also be built from a cloned repository with npm install, followed by npm run build, and then started with Node against the generated dist/index.js file. The README provides that manual path but uses a placeholder filesystem path in its client configuration, so the actual path must be supplied by the operator.

Tools and capabilities

The listed Meta tools include token exchange, token refresh, token debugging, app information, webhook subscription creation, and webhook subscription listing. Instagram tools cover photo, video, Reel, Story, and carousel publishing; media retrieval and deletion; container-status checks; insights; comment controls; comment and reply management; profile data; account insights; business discovery; and collaboration invites. Threads tools documented by the README extend the server to publishing, conversations, replies, search, profiles, locations, mentions, oEmbed, insights, and deletion.

The project also documents two MCP resources for Instagram and Threads profiles and two prompts for cross-platform publishing and analytics reporting. Rate-limit tracking uses the x-app-usage response header.

Limitations and notes

Deleting Instagram media or comments is irreversible and requires the relevant permissions. Instagram insight metric names changed in newer Graph API versions; deprecated fields such as impressions and video_views should not be used where the API now expects metrics such as views, reach, saved, shares, or reposts. Access tokens and app secrets should be kept outside prompts and source-controlled configuration.