Openpost vs Meta MCP

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

Openpost logoOpenpostSocial MediaManage social publishing workflows through OpenPost40FairAuth: 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 Openpost for social media work; 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?

Openpost logoChoose Openpost when

  • You need dedicated capabilities in the Social Media domain.
Explore Openpost

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.

SpecOpenpost logoOpenpostMeta MCP logoMeta MCP
CategorySocial MediaSocial Media
Quality signal40/100 · Fair68/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingFreeFree
Required env varsNone listedINSTAGRAM_ACCESS_TOKENINSTAGRAM_USER_IDINSTAGRAM_MESSAGING_ACCESS_TOKENINSTAGRAM_PAGE_IDTHREADS_ACCESS_TOKENTHREADS_USER_IDMETA_APP_IDMETA_APP_SECRET
Verified ownerCommunity listingCommunity listing
GitHub stars75330
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed66

Tools & capabilities

Openpost tools

No tool names declared yet. Check the project README from 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.

Openpost

No confirmed install command for Openpost yet — follow the setup steps linked from its listing page rather than a guessed package name.

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

Openpost is categorized under Social Media and uses an install path we have not confirmed yet. Meta MCP belongs to Social Media and uses a local stdio subprocess. Pick Openpost 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. Openpost has no confirmed install command yet — follow its own setup instructions.

Openpost is listed as free. 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 openpost and mikusnuz-meta-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Openpost has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 753 GitHub stars. Meta MCP has 68/100 (Great) with 6 views, 0 installs and 30 GitHub stars.