INSSIST vs Meta MCP

A side-by-side look at the INSSIST and Meta MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

INSSIST logoINSSISTSocial Media · Local subprocess (stdio)Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.67GreatAuth: not declaredMeta MCP logoMeta MCPSocial Media · Local subprocess (stdio)Full-coverage MCP server for Instagram Graph API v25.0, Threads API & Meta platform — 57 tools for publishing, comments, insights, hashtags, DMs, and token management.68GreatAuth: api key required

Verdict: choose INSSIST for social media work as a local process; choose Meta MCP for social media as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

INSSIST logoChoose INSSIST when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: INSSIST_MCP_PORT, INSSIST_MCP_HOME.
  • You want tools like account_info, account_switch, antibot_export.
Explore INSSIST

Meta MCP logoChoose Meta MCP when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: INSTAGRAM_ACCESS_TOKEN, INSTAGRAM_USER_ID, INSTAGRAM_MESSAGING_ACCESS_TOKEN, INSTAGRAM_PAGE_ID, THREADS_ACCESS_TOKEN, THREADS_USER_ID, META_APP_ID, META_APP_SECRET.
  • You want tools like meta_exchange_token, meta_refresh_token, meta_debug_token.
Explore Meta MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecINSSIST logoINSSISTMeta MCP logoMeta MCP
CategorySocial MediaSocial Media
Quality signal67/100 · Great68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingFreemiumFree
Required env varsINSSIST_MCP_PORTINSSIST_MCP_HOMEINSTAGRAM_ACCESS_TOKENINSTAGRAM_USER_IDINSTAGRAM_MESSAGING_ACCESS_TOKENINSTAGRAM_PAGE_IDTHREADS_ACCESS_TOKENTHREADS_USER_IDMETA_APP_IDMETA_APP_SECRET
Verified ownerCommunity listingCommunity listing
GitHub stars3130
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools6066

Tools & capabilities

INSSIST tools 60

  • account_infoList connected browser instances, the account each is logged into, other available accounts, and the default target. `proTrialDaysLeft` > 0 means PRO write tools answer for that many more days.
  • account_switchSwitch the browser profile to another logged-in account (see account_info). Later calls act as it; reloads open Instagram tabs. Switching to the active account is a no-op.
  • antibot_exportExport the full antibot follower analysis (risk + type per follower) to a CSV file; returns the path. (Requires INSSIST PRO.)
  • antibot_reportFollower quality analysis from the last antibot scan: totals by risk and type, plus the flagged (unreviewed high/medium-risk) followers. Empty until a scan has run. (Requires INSSIST PRO.)
  • antibot_scanStart a follower scan scoring each follower bot/suspicious/fresh/clean. Runs in the background; poll antibot_report. Detection only — removes no one. (Requires INSSIST PRO.)
  • comment_addPost a comment on a post. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_deleteDelete a comment — your own, or any on your own post. Permanent. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_likeLike a comment, or unlike with `unlike: true`. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_replyReply to a comment. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comments_listList comments on a post and their replies. (Requires INSSIST PRO.)
  • dm_acceptAccept a pending DM message request, moving it into the inbox. (Requires INSSIST PRO.)
  • dm_listList recent DM conversations, the last message, and whether a reply is awaited. Returns Instagram's single inbox page, which cannot be paged further. Read-only.
  • +48 more on the listing page

Meta MCP tools 66

  • meta_exchange_tokenExchange a short-lived token for a long-lived token (valid ~60 days). Requires META_APP_ID and META_APP_SECRET.
  • meta_refresh_tokenRefresh a long-lived token before it expires. Returns a new long-lived token.
  • meta_debug_tokenDebug/inspect an access token to check validity, expiration, scopes and associated user.
  • meta_get_app_infoGet Meta App basic information (name, category, namespace, etc.).
  • meta_subscribe_webhookSubscribe to webhook notifications for an object (e.g., 'instagram', 'page'). Requires META_APP_ID and META_APP_SECRET.
  • meta_get_webhook_subscriptionsList current webhook subscriptions for the Meta App.
  • ig_publish_photoPublish a photo to Instagram. Two-step process: creates container then publishes. Requires image_url (publicly accessible HTTPS URL).
  • ig_publish_videoPublish a video to Instagram feed. Waits for video processing before publishing.
  • ig_publish_carouselPublish a carousel (album) post with 2-10 images/videos. Each item needs an image_url or video_url.
  • ig_publish_reelPublish a Reel (short video). Waits for video processing.
  • ig_publish_storyPublish a Story (image or video). Stories disappear after 24 hours.
  • ig_get_container_statusCheck the processing status of a media container (useful for videos).
  • +54 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

INSSIST

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "inssist": {
      "command": "npx",
      "args": [
        "-y",
        "@inssist/mcp"
      ],
      "env": {
        "INSSIST_MCP_PORT": "YOUR_INSSIST_MCP_PORT_HERE",
        "INSSIST_MCP_HOME": "YOUR_INSSIST_MCP_HOME_HERE"
      }
    }
  }
}

Meta MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mikusnuz-meta-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-mcp"
      ],
      "env": {
        "INSTAGRAM_ACCESS_TOKEN": "YOUR_INSTAGRAM_ACCESS_TOKEN_HERE",
        "INSTAGRAM_USER_ID": "YOUR_INSTAGRAM_USER_ID_HERE",
        "INSTAGRAM_MESSAGING_ACCESS_TOKEN": "YOUR_INSTAGRAM_MESSAGING_ACCESS_TOKEN_HERE",
        "INSTAGRAM_PAGE_ID": "YOUR_INSTAGRAM_PAGE_ID_HERE",
        "THREADS_ACCESS_TOKEN": "YOUR_THREADS_ACCESS_TOKEN_HERE",
        "THREADS_USER_ID": "YOUR_THREADS_USER_ID_HERE",
        "META_APP_ID": "YOUR_META_APP_ID_HERE",
        "META_APP_SECRET": "YOUR_META_APP_SECRET_HERE"
      }
    }
  }
}

Frequently asked questions

INSSIST is categorized under Social Media and uses a local stdio subprocess. Meta MCP belongs to Social Media and uses a local stdio subprocess. Pick INSSIST for social media work and Meta MCP for social media.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

INSSIST is listed as freemium — a free tier with paid plans. Meta MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add inssist and mikusnuz-meta-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, INSSIST has a quality signal of 67/100 (Great) with 1 views, 0 installs and 31 GitHub stars. Meta MCP has 68/100 (Great) with 6 views, 0 installs and 30 GitHub stars.