Sf MCP vs Postwire MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sf MCP vs Postwire MCP
In-depth architectural comparison of the Sf MCP and Postwire 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
Sf MCP
Social Media · Local stdio
Quality: 57/100 (Good) | Auth: other
Postwire MCP
Social Media · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Sf MCP if you need specialized Social Media tools running via a local process. Choose Postwire 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 Sf MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Paid Service).
You have access to required keys: ONBOARD_API_CLIENT_ID.
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.
Post to TikTok, Instagram, YouTube, X, LinkedIn, Bluesky, Telegram, Mastodon & Discord from any AI agent via one MCP tool (posttosocial). Connect accounts once; flat per-brand pricing. Install: npx -y postwire-mcp.
Category & Scope
Tools & Capabilities Breakdown
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
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).
Sf MCP is categorized under Social Media and uses a local stdio subprocess. In contrast, Postwire MCP belongs to Social Media using local stdio subprocess. Select Sf MCP when you need capabilities focused on social media and Postwire MCP when you require tools for social media.
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']}]
+28 more tools listed on main page
Postwire MCP Tools (5)
generate_posts
Smart Distribute — PostWire's native AI writer. Give ONE prompt (and optional media) and it writes the BEST NATIVE post for EACH platform: correct character limits, hashtag rules, SEO title+tags for YouTube, hook-first captions for TikTok/Reels, professional framing for LinkedIn (link-in-comment), thread-friendly text for X (link-in-reply), CamelCase tags for Mastodon, and more. It does NOT send the same text everywhere — each platform gets its own optimized draft. Returns { drafts: { <platform>: { text, title?, tags? } } }. Review/edit, then pass to post_to_social as per_platform.
post_to_social
Publish to one or more social platforms via PostWire, in parallel. For best results, first call generate_posts to get a NATIVE draft per platform, then pass them here as `per_platform` (PostWire never just copies the same text everywhere). Or pass a single `text` for a quick same-everywhere post. Connect accounts first at https://postwire.io/dashboard.html. Returns per-platform results (each has an id you can pass to get_post_status).
get_post_status
Check the processing/publish status of a post previously created with post_to_social.
list_platforms
List the social platforms PostWire supports and the fields each needs.
my_account
Show the PostWire account: plan, monthly usage, and connected platforms.