Skip to content
For developers

MCP overview

What the ActuallyCare MCP server exposes, how Claude connects to it, and where to start.

Last updated

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude work safely with outside systems. ActuallyCare runs an MCP server, which means Claude can look up your escrows, check today's appointments, or draft a follow-up for a hot lead — using your real CRM data, with your permission, under your account.

If you just want to connect Claude, you only need one thing — the connector URL:

https://mcp.actuallycare.com/mcp

Paste it into Claude following the quickstart and you'll be connected in a few minutes. The rest of this page is the map of what's behind that URL.

What the server exposes#

Tools. Actions covering every part of the CRM. Most are named entity first (escrows_list, clients_create, leads_convert); workflow tools are verb first (get_dashboard_stats, draft_email). The tool reference is generated straight from the server's registry, so the live counts and parameters there are always current.

Prompts. 13 built-in prompts — ready-made workflows like create_escrow, daily_summary, hot_leads_followup, and closing_checklist that package a multi-step task into one request. Each has a generated reference page under Prompts.

Which tools Claude can use#

To keep conversations fast, the server doesn't push the full catalog into every chat. It advertises a set of everyday tools — lists and lookups for your main records, creating and updating escrows, clients, leads, contacts, listings, and appointments, today's calendar, drafts, checklists, deadlines, and calculators — plus three discovery tools.

Claude can only call the tools it's been given, so the advertised set is what Claude can do. The discovery tools can describe the rest of the catalog, but Claude can't run those tools yet. Custom apps and scripts are different: they can call any tool by name. See Build a custom app.

Connection details#

Server URLhttps://mcp.actuallycare.com/mcp
TransportStreamable HTTP (JSON-RPC over POST, with an SSE stream on the same endpoint)
Legacy transportHTTP+SSE at https://mcp.actuallycare.com/sse, for older clients
Protocol version2025-03-26

Authentication#

  • OAuth 2.1 — the normal path for Claude users. Adding the connector opens an ActuallyCare login and a consent screen listing exactly what Claude may do. Access tokens last 24 hours and refresh tokens rotate automatically, so you stay connected without re-approving. To disconnect, remove the connector in Claude's own settings.
  • API key — custom clients can send the same 64-character keys the REST API uses, in the X-API-Key header. See Authentication.
  • JWT — a Bearer token from POST /v1/auth/login also works, which is handy when your app already manages ActuallyCare user sessions.

Supported clients#

ClientStatusGuide
Claude.ai (web)SupportedConnect Claude on the web
Claude DesktopSupportedConnect Claude Desktop
Claude mobile (iOS and Android)Supported — connectors added on the web appear in the app automaticallyUse ActuallyCare on mobile
Claude CodeSupportedConnect Claude Code
Any standards-compliant MCP clientSupportedBuild a custom MCP app
ChatGPTNot yet—
GeminiNot yet—

Where to go next#

  • Agents and non-technical users: the quickstart walks you through connecting Claude step by step, and What can I ask? shows what to do once you're connected.
  • Copying records into any AI: every record in the CRM has a Copy for AI action that pastes a compliant snapshot plus a live MCP reference — useful even before you connect.
  • Developers: Build a custom MCP app covers connecting from your own code, and API vs MCP explains when to use the REST API instead.