CRM Solid MCP vs Sf MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
CRM Solid MCP vs Sf MCP
In-depth architectural comparison of the CRM Solid 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
CRM Solid MCP
Social Media · Remote HTTP/SSE
Quality: 74/100 (Great) | Auth: API Key required
Sf MCP
Social Media · Local stdio
Quality: 59/100 (Good) | Auth: other
Verdict Summary: Choose CRM Solid MCP if you need specialized Social Media tools running via a hosted cloud SSE transport. 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 CRM Solid MCP when:
You need dedicated capabilities in the Social Media domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: CRMSOLID_API_KEY.
Read and reply to social DMs, schedule posts, and manage CRM contacts and deals across Telegram, X, WhatsApp, Instagram and email from your AI assistant.
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
CRM Solid MCP Tools (13)
crm_list_social_accounts
Lists connected accounts per platform
crm_list_social_conversations
Filters by `platform`, `status`, `contactId`, `unreadOnly
crm_get_social_conversation
One conversation plus its last 10 messages
crm_list_social_messages
Message history, paged with `beforeMessageId
crm_send_social_message
Sends a DM and pauses the AI agent for that contact
crm_mark_social_conversation_read
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).
CRM Solid MCP is categorized under Social Media and uses a remote streaming HTTP/SSE transport. In contrast, Sf MCP belongs to Social Media using local stdio subprocess. Select CRM Solid MCP when you need capabilities focused on social media and Sf MCP when you require tools for social media.
Totals per platform, plus the 10 oldest waiting replies
crm_list_social_posts
Filters by `status`, `platform`, `fromDate`, `toDate
crm_get_social_post
One post with its media, target account and outcome
crm_schedule_social_post
Queues a post per target account, **never publishes by accident
crm_update_social_post
Edits content, time or media while the post is still pending
crm_cancel_social_post
Cancels a post that has not gone out
+1 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']}]