Work from real CRM context
Let assistants use the accounts, contacts, leads, deals, products, and activities already in your workspace.
CRM with MCP integration
A CRM with MCP for permission-aware AI workflows.
Connect ChatGPT, Claude.ai, Claude Code, Cursor, Codex, and other compatible clients to Anvil CRM through OAuth 2.1. Choose one workspace, grant explicit scopes, and keep every action inside the member's live permissions.
No card details required.
Turn CRM context into useful action while keeping control.
MCP gives AI assistants a structured way to interact with Anvil. Your team can use a compatible assistant to read, create, update, and analyze CRM records while Anvil's existing workspace permissions keep access scoped to the right people and data.
Built for the day-to-day
Practical capabilities, explained plainly.
Build useful sales workflows
Ask for reports, identify next actions, research account context, and create workflows that fit the way your team sells.
Keep access permission-aware
MCP actions respect the workspace access and permissions configured in Anvil.
What is an MCP CRM?
A CRM that exposes defined tools, not an unrestricted database connection.
The Model Context Protocol gives an AI client a standard way to discover and call tools. Anvil's remote MCP server describes CRM objects, readable fields, filters, and allowed actions. The assistant receives structured results instead of browser access or database credentials.
Every connection is bound to one workspace during OAuth consent. Anvil then intersects the token scopes with the stored grant, workspace switches, plan entitlements, role permissions, record visibility, and pipeline access on every call. A scope can narrow access; it cannot grant authority the member does not already have.
Connection sequence
Connect a compatible client in four controlled steps.
- 1
An admin enables agents
On Pro, a workspace admin turns on agent access under Settings → AI agents. Write access remains a separate switch and can stay off.
- 2
Add the remote endpoint
Configure the client with https://app.anvilcrm.com/api/mcp. Anvil publishes OAuth authorization and protected-resource metadata for discovery.
- 3
Choose workspace and scopes
Sign in, select exactly one workspace, and approve read, write, correction, or delete scopes. The client never chooses a tenant from unverified input.
- 4
Inspect before acting
Call whoami first to see the workspace, effective scopes, CRM access, and permission matrix. Use discovery tools before sending record fields.
Remote MCP endpoint
https://app.anvilcrm.com/api/mcpOAuth scopes
Grant only the class of action the workflow needs.
| Scope | Allows | Important boundary |
|---|---|---|
anvil:read | Object discovery, records, activities, timelines, pipeline summaries, and reports | Results still follow record, field, pipeline, and module permissions |
anvil:write | Create and update CRM records, activities, relationships, lifecycle actions, and commercials | Disabled when the workspace write switch is off; writes use revision or idempotency controls |
anvil:correct | Audited corrections to current or historical deal closure episodes | Separate from ordinary write access because it changes commercial history |
anvil:delete | Delete a record or activity occurrence | Requires an explicit confirmation flag; CRM record deletion is soft deletion |
Tool coverage
Move from discovery to a fenced CRM action.
Discover
Use list_objects and describe_object to learn available object types, fields, list columns, filters, and write contracts instead of guessing payloads.
Read and diagnose
Search or list records, inspect activities and timelines, get pipeline summaries, and find work that needs attention within the caller's visibility.
Act with concurrency controls
Create records and tasks with idempotency keys. Update existing records with their expected revision so a stale assistant cannot overwrite a newer human change.
Handle lifecycle explicitly
Preview stage, close, reopen, conversion, ownership, and commercial actions before applying them. Dedicated tools preserve required values and lifecycle history.
Example requests
Give the assistant a goal and a review boundary.
“Show the open deals I can see that have no completed activity in the last 14 days. Do not change anything.”
“Summarize the visible timeline for Meridian Systems and list unresolved next actions with their owners.”
“Preview moving this deal to Proposal and tell me which values or permissions are missing. Do not apply the change.”
“Draft five follow-up tasks from this pipeline review. Show the proposed titles, owners, and due dates before creating them.”
Safeguards and limitations
Safeguards and limitations to understand before connecting.
Live permissions
Every call re-checks membership, roles, record access, pipeline visibility, plan entitlements, scopes, and workspace agent switches.
Explicit high-impact confirmation
Deletion and workspace-structure tools require the assistant to restate the change, obtain confirmation in the same turn, and send confirm: true.
Auditable agent activity
Tool calls record the grant, member, client, tool, outcome, duration, and touched record IDs, but not prompts, inputs, results, or field values.
Immediate revocation
A member can revoke their grant and an admin can revoke any workspace grant. Disabling workspace access or removing membership also blocks calls.
Bounded requests
Lists are paginated, request and response sizes are capped, rate limits apply, and writes use revision fences or idempotency keys.
Human review still matters
The server enforces authorization and data contracts; it cannot guarantee that an assistant's interpretation, summary, or proposed business decision is correct.
Continue evaluating Anvil
Explore the details that matter to your team.
Review agent securityUnderstand workspace isolation, live authorization, audit records, retention, and revocation.Read moreMap MCP to B2B workflowsSee the account, pipeline, activity, and reporting loop an assistant can support.Read moreCheck Pro pricingMCP access is a Pro capability; compare current team costs and plan limits.Read more
Frequently asked questions
Learn more about Anvil CRM.
What is an MCP CRM?
An MCP CRM connects to AI assistants through the Model Context Protocol, giving them structured access to CRM tools and data within defined permissions.
Which AI assistants work with Anvil MCP?
Anvil MCP uses the remote streamable HTTP transport and works with compatible clients including ChatGPT, Claude.ai, Claude Code, Cursor, and Codex. Client support changes independently, so confirm that your chosen client supports remote MCP servers and OAuth.
What can an AI assistant do with Anvil CRM?
Depending on its OAuth scopes and the member's live permissions, an assistant can inspect CRM structure, search and read records, review pipelines and timelines, create or update records and activities, run reports, and perform explicitly confirmed structure or deletion actions.