Meta MCP vs PlanVortex
A side-by-side look at the Meta MCP and PlanVortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Meta MCP for social media work as a local process; choose PlanVortex 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?
Choose 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.
Choose PlanVortex when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLANVORTEX_CLIENT_ID, PLANVORTEX_CLIENT_SECRET, PLANVORTEX_ORGANIZATION_ID, PLANVORTEX_MCP_ALLOW_AI, PLANVORTEX_MCP_READ_ONLY, PLANVORTEX_MCP_AUTH_TOKEN, PLANVORTEX_MCP_UPLOAD_DIRS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 68/100 · Great | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | INSTAGRAM_ACCESS_TOKENINSTAGRAM_USER_IDINSTAGRAM_MESSAGING_ACCESS_TOKENINSTAGRAM_PAGE_IDTHREADS_ACCESS_TOKENTHREADS_USER_IDMETA_APP_IDMETA_APP_SECRET | PLANVORTEX_CLIENT_IDPLANVORTEX_CLIENT_SECRETPLANVORTEX_ORGANIZATION_IDPLANVORTEX_MCP_ALLOW_AIPLANVORTEX_MCP_READ_ONLYPLANVORTEX_MCP_AUTH_TOKENPLANVORTEX_MCP_UPLOAD_DIRS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 30 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 66 | Not listed |
| Full listing | View Meta MCP | View PlanVortex |
Tools & capabilities
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
PlanVortex tools
No tool names declared yet. Check the project README from 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.
Meta MCP
{
"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"
}
}
}
}
PlanVortex
{
"mcpServers": {
"planvortex": {
"command": "npx",
"args": [
"-y",
"planvortex-mcp"
],
"env": {
"PLANVORTEX_CLIENT_ID": "YOUR_PLANVORTEX_CLIENT_ID_HERE",
"PLANVORTEX_CLIENT_SECRET": "YOUR_PLANVORTEX_CLIENT_SECRET_HERE",
"PLANVORTEX_ORGANIZATION_ID": "YOUR_PLANVORTEX_ORGANIZATION_ID_HERE",
"PLANVORTEX_MCP_ALLOW_AI": "YOUR_PLANVORTEX_MCP_ALLOW_AI_HERE",
"PLANVORTEX_MCP_READ_ONLY": "YOUR_PLANVORTEX_MCP_READ_ONLY_HERE",
"PLANVORTEX_MCP_AUTH_TOKEN": "YOUR_PLANVORTEX_MCP_AUTH_TOKEN_HERE",
"PLANVORTEX_MCP_UPLOAD_DIRS": "YOUR_PLANVORTEX_MCP_UPLOAD_DIRS_HERE"
}
}
}
}
Frequently asked questions
Meta MCP is categorized under Social Media and uses a local stdio subprocess. PlanVortex belongs to Social Media and uses a local stdio subprocess. Pick Meta MCP for social media work and PlanVortex 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.
Meta MCP is listed as free. Auth: api key required. PlanVortex has no declared pricing — check the project's own site. 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 mikusnuz-meta-mcp and planvortex as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Meta MCP has a quality signal of 68/100 (Great) with 6 views, 0 installs and 30 GitHub stars. PlanVortex has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.