Business operationsPublic source

CRM MCP Server

Unified CRM MCP server with 28 tools across 4 backends — Salesforce, HubSpot, Zoho CRM, and Pipedrive. Unified contacts, companies, deals, activities, pipelines, and notes with associations, search, and lifecycle…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Unified schema — agents see consistent types (Contact, Company, Deal, Activity, Pipeline, Note) regardless of backend

Feature-flagged backends — compile only what you need (--features salesforce,hubspot)

Full CRM lifecycle — search contacts, manage deals through pipeline stages, log activities, attach notes

No credential exposure — tokens stay in env vars, never reach LLM context

Single binary — no Node.js, no Python, no runtime dependencies

Architecture

How CRM MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

CRM MCP Server

Validates the request and owns 28 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

CRM MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask CRM MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

28 named tools

list_contacts

List contacts with optional search query

read only

get_contact

Get a contact by ID

read only

create_contact

Create a new contact

internal write

update_contact

Update an existing contact

internal write

search_contacts

Search contacts by name, email, or custom query

read only

list_companies

List companies/accounts

read only

get_company

Get a company by ID

read only

create_company

Create a new company/account

internal write

update_company

Update an existing company

internal write

list_deals

List deals/opportunities

read only

get_deal

Get a deal by ID with stage and value

read only

create_deal

Create a new deal/opportunity

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

14 read only12 internal write2 external write

The registry manifest declares read only, internal write, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Long-running tasks

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-crm --features all-backends

MCP client configuration

export SALESFORCE_INSTANCE_URL="https://yourorg.my.salesforce.com"
export SALESFORCE_TOKEN="00D..."

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring