Model Context Protocol (MCP)

Query Salfio from Claude, Cursor, and other MCP-aware clients using the same tools your team already uses.

Salfio speaks the Model Context Protocol. If your AI assistant is MCP-aware — Claude Desktop, Claude.ai web, Cursor, the MCP Inspector — it can connect to mcp.salfio.com and use the same client/activity/dashboard data your team sees in the app.

Once connected, an MCP client sees a set of tools mapped 1:1 to the Salfio Public API:

• List and retrieve clients — retrieving a single client also returns its AI churn-risk assessment (churnRiskLevel: high | medium | low, plus churnSignals, short evidence sentences grounded in captured conversations) and its AI upsell-opportunity assessment (upsellSignalsLevel: high | medium | low, plus upsellSignals and upsellServices — the services from your catalog the signals point to, each with serviceId and title; a high level always comes with at least one matched service), once enough conversation data has been analyzed
• Create, update, delete clients
• Read a client's recent activities (emails + calls), or scope the search to a date range to look further back
• Write a note onto a client (recorded as a note activity, attributed to a user)
• Read the AI-generated cards (briefing, wins/traction, risks/frictions, topics) for a client
• List the organization's integrations, and list the channels a Slack integration's bot is in — the discovery step for setting up assignment rules
• Read and replace a client's assignment rules — bind a Slack channel (or another integration) to a client so its communications are assigned automatically
• Read and maintain the organization's services catalog — the services you sell, described so the assistant can spot upsell opportunities
• Read the organization summary and users

Every tool is scoped to your organization. Cross-tenant reads return "not found" — the same no-leak rule the REST API enforces.

Pick based on what your client supports:

• Connect from Claude.ai web — OAuth, the recommended path for the web client.
• Connect from Claude Desktop (and other API-key clients) — paste a Salfio API key into the client config.

MCP shares the same rate-limit buckets as the REST API: 100 requests per minute at the organization level, 50 per minute per tool. A single team can't double its quota by splitting work across REST and MCP — the buckets are deliberately unified.

See Rate Limits for the full policy.

MCP tools that write (create_client, update_client, delete_client, create_note, set_assignment_rules, create_service, update_service, delete_service) make the same changes the API would. Every mutation is subject to the usual authorization and audit trail. An org_oauth connection carries organization scope — suitable for a shared team assistant, as its scope isn't tied to any one user's role — but it carries no user identity at all. A tool that must attribute its write to a person therefore either asks you which one (create_note's author_user_id) or is unavailable on that connection (create_task_routine, since a routine runs as its creator). See the Claude.ai web guide for how to pick between user-scoped and org-scoped grants.