Meta MCP vs Sf MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Meta MCP vs Sf MCP
In-depth architectural comparison of the Meta MCP and Sf MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Meta MCP
Social Media · Local stdio
Quality: 68/100 (Great) | Auth: API Key required
Sf MCP
Social Media · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose Meta MCP if you need specialized Social Media tools running via a local process. Choose Sf MCP if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Meta MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: 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.
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.
Connect AI agents to Signal Found's proprietary Reddit outreach network. Find prospects posting about problems your product solves, send personalized DMs at scale via your own Reddit account or a managed bot network of hundreds of accounts, and manage a full outreach CRM — all without leaving your AI client.
Category & Scope
Tools & Capabilities Breakdown
Meta MCP Tools (66)
meta_exchange_token
Exchange a short-lived token for a long-lived token (valid ~60 days). Requires META_APP_ID and META_APP_SECRET.
meta_refresh_token
Refresh a long-lived token before it expires. Returns a new long-lived token.
meta_debug_token
Debug/inspect an access token to check validity, expiration, scopes and associated user.
meta_get_app_info
Get Meta App basic information (name, category, namespace, etc.).
meta_subscribe_webhook
Subscribe to webhook notifications for an object (e.g., 'instagram', 'page'). Requires META_APP_ID and META_APP_SECRET.
meta_get_webhook_subscriptions
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Meta MCP is categorized under Social Media and uses a local stdio subprocess. In contrast, Sf MCP belongs to Social Media using local stdio subprocess. Select Meta MCP when you need capabilities focused on social media and Sf MCP when you require tools for social media.
List current webhook subscriptions for the Meta App.
ig_publish_photo
Publish a photo to Instagram. Two-step process: creates container then publishes. Requires image_url (publicly accessible HTTPS URL).
ig_publish_video
Publish a video to Instagram feed. Waits for video processing before publishing.
ig_publish_carousel
Publish a carousel (album) post with 2-10 images/videos. Each item needs an image_url or video_url.
ig_publish_reel
Publish a Reel (short video). Waits for video processing.
ig_publish_story
Publish a Story (image or video). Stories disappear after 24 hours.
ig_get_container_status
Check the processing status of a media container (useful for videos).
+54 more tools listed on main page
Sf MCP Tools (40)
sf_health
Preflight check for MCP -> onboard_api connectivity and auth context.
Use this first in a new session to confirm:
- backend is reachable
- current MCP session auth state
- whether a default client id is configured
login_with_client_id
Authenticate MCP session to a Signal Found client account.
Run this at the start of each session before business tools.
Most tools require authenticated context and will use this session client id unless
you pass an explicit `client_id` argument.
current_client_context
Return the currently authenticated client context for this MCP server session.
agent_quickstart
Zero-context onboarding playbook for agents using this MCP server.
Returns the recommended call sequence, common guardrails, and recovery hints.
logout_client_context
Clear the active authenticated client context for this MCP server session.
list_products
List all products for a client (slug, display_name, product_unique, folder_id).
get_product_tree
Get nested folders and products for a client, equivalent to frontend product tree.
create_new_account
Create a brand-new Signal Found client account for onboarding.
Requires:
- `business_name`
- `email`
Returns created `client_id` and (by default) logs this MCP session into it.
Next step after success:
- call `create_new_product`
create_new_product
Create a product and initialize the agent onboarding session context.
The response includes:
- product creation result
- context packet (existing artifacts + screenshot uri)
- prompt pack + version metadata
Prerequisite:
- authenticated session via `login_with_client_id` (or provide `client_id` explicitly)
Next step after success:
- call `run_full_agentic_onboarding` (or run staged tools manually)
get_onboarding_prompt_pack
Fetch server-curated prompt contracts that define required onboarding outputs.
Use this when an agent needs exact formatting/expectations before generating:
- clarifications
- conversation transcript
- market positioning
- keywords/subreddits
Use `artifact` for focused contracts:
- clarifications
- market_position
- conversation
- keywords
- subreddits
submit_onboarding_artifacts
Validate and persist core onboarding artifacts for a product/session.
Prerequisites:
- prompt pack must be acknowledged for `session_id`
- payloads should match the artifact schemas below
Common use:
- called by `run_full_agentic_onboarding`
- can also be used for staged/recovery runs
Expected formats:
- market_position: patch object with market position keys
- conversion_notes: {'Product Name','Payment Terms/Plans','General Notes'}
- funnels: [{'url','description','primary_use_case', optional 'qualification'}]
submit_agent_targeting
Persist targeting artifacts (keywords/subreddits) and return policy/preview.
Prerequisites:
- prompt pack must be acknowledged for `session_id`
- artifacts should already be saved for best results
Typical next step:
- approve targeting (done automatically by `run_full_agentic_onboarding` when enabled)
Formats:
- keywords: list[str]
- subreddit_groups: [{'subreddits': ['name1','name2']}]