CRM MCP server

Connect your AI tools to your CRM

Use an MCP-compatible agent to look up contacts, update deals, and manage follow-up tasks. Connect it with your CRM URL and access key, then review its work in the dashboard.

Create a workspace Connect an agent

What CRM MCP server means

The term explained, followed by how it works in Agent Native CRM.

What MCP means

MCP stands for Model Context Protocol. It is a way for compatible AI tools to discover and use features provided by another application.

What this server provides

The CRM makes its operations available as MCP tools. Your agent can read contacts, save notes, update deals, and create tasks using its workspace access key.

What to check before you choose

For CRM MCP server, check these details before connecting your team or software.

Connection

Question to askWhat does my client need?

Agent Native CRMAn MCP client that supports this server’s HTTP requests, the server URL, and a workspace access key.

Available tools

Question to askWhich CRM tasks can it perform?

Agent Native CRMIt can use the CRM’s record, task, deal, and settings operations, subject to its role.

Permissions

Question to askDoes MCP give agents extra access?

Agent Native CRMMCP requests use the same roles and checks as requests made directly to the API.

Sending

Question to askCan the CRM tools deliver outreach?

Agent Native CRMThe tools can store a draft and record an outcome. Sending requires your own external tool.

What you can do

Here are the actions you can take, followed by the API requests a developer or agent can use for each one.

Set the URL and access key

Configure your client to reach the CRM’s /mcp endpoint with a bearer access key. Consult the setup guide for request examples.

GET /v1/openapi.json
GET /v1/skill
GET /v1/me

Read the fields and save a contact

Ask the agent to inspect the workspace fields and its own role. It can then add a company using the fields the workspace accepts.

GET /v1/schema
GET /v1/me
POST /v1/companies

Manage the next task

The agent can list tasks, claim one, record the result, and create a follow-up. The dashboard shows the same work.

GET /v1/tasks
POST /v1/tasks/{id}/claim
POST /v1/tasks/{id}/complete
POST /v1/tasks

Add the details your team needs

With the right role, the agent can create custom fields, record types, and saved views through the available CRM tools.

POST /v1/schema/fields
POST /v1/schema/objects
POST /v1/views
GET /v1/views/{id}/records

Agent Native CRM

Ask your agent to update the CRM, then check the result.

How you stay in control

Choose who can change data, review important work, and correct mistakes. Some checks are built in; optional policies need to be configured.

Use a separate key

Connect the client with a key for its own workspace identity. You can revoke that key without changing another agent’s credentials.

Keep permission checks

Requests that exceed the agent’s role are refused. MCP uses the same access rules as the direct API.

Give the agent the guide

The setup guide explains field names, task handling, and expected responses so your agent has instructions for using the tools.

Check what was saved

Inspect the dashboard or activity history after an update. The history identifies the actor and any source details it supplied.

POST/v1/tasks/{id}/claim

Connection and response details

These notes explain the fields or connection settings used in this example. The setup guide includes the complete request and response formats.

Read the setup guide

GET /mcp

tools: The available CRM tools. Request the current list from the server.
names: Action names such as getSchema, createCompany, and claimTask.
arguments: The fields each tool expects in its request.
transport: JSON-RPC requests sent by HTTP POST to /mcp.
auth: A workspace access key and the role associated with it.
docs: The setup guide at /skill.md, with usage examples.

What you provide

Use the CRM for records and tasks, and connect the other tools your workflow needs.

Use a compatible AI client

The CRM supplies tools, not the AI client itself. Your chosen client must support the server’s connection and authentication method.

Send with other tools

The MCP server does not send sales emails or messages. Your agent must use its own sending tool and log the outcome here.

Run agents in your own environment

Connecting the MCP server does not start a hosted agent or a schedule. You control when and where your agent runs.

Common questions

Practical answers about setup, capabilities, and what you need to provide.

What is a CRM MCP server?

It exposes CRM actions as tools that a compatible AI client can use. This server provides tools for contacts, deals, tasks, and workspace settings.

How do I connect a client?

Use the /mcp endpoint with a bearer access key for your workspace. Your client must support the server’s HTTP connection and authentication method.

Do MCP tools have different permissions?

No. The key identifies the caller and its role. The same permission checks apply whether a request comes through MCP or the REST API.

Can an agent send messages through this server?

No. It can save a message draft in a task and record the outcome. The agent needs a separate email or messaging tool to send it.

Related guides

Learn more about the connection options and examples that fit your work.

Start with your first contact

Create a workspace, connect your agent, and add your first contact. Choose a plan based on how many records and activity entries you need to store.

Create a workspace See pricing