Skip to main content
The Model Context Protocol (MCP) is an open standard developed by Anthropic that lets AI models securely connect to external data sources and tools. Instead of copy-pasting data into a chat window, MCP gives AI agents a typed, structured interface to read from and write to real systems.

​
Why use MCP?

Traditional API integrations require you to build adapters for each AI tool you want to use. MCP standardises this: your AI client (Claude, Cursor, a custom agent) speaks one protocol, and any MCP server — including AmDital — plugs straight in.
  • No custom integration code per AI tool
  • Typed inputs and outputs — the AI knows exactly what each tool accepts
  • Auth happens once at connection (your workspace bearer token), not per call
  • Works with any MCP-compatible client: Claude Desktop, Cursor, VS Code, and more

​
AmDital’s MCP tools — CRM

AmDital ships 6 typed tools over your CRM data (leads, contacts, deals, companies). Every tool is discoverable at runtime — your AI client fetches the schema automatically via tools/list. MCP tool coverage today is CRM-only. See the full Tool Reference for schemas and examples.
MCP is not the primary way to use AmDital — it’s a protocol adapter for AI agents and automations that need programmatic access to your CRM data. Most workspace members should use the app directly; MCP is for integrators and AI-assisted workflows.

​
Use cases

AI Assistants

Let Claude, ChatGPT, or any LLM read and write your CRM data in natural language — no custom integration code required.

Automation Workflows

Trigger CRM lookups or updates from n8n, Zapier AI steps, or custom agent pipelines using standard MCP tool calls.

Custom Agents

Build fully custom AI agents in Python, TypeScript, or any language using the open MCP SDK and AmDital’s CRM tools.

Team Copilots

Create internal copilots that surface the right pipeline context — leads, deals, contacts — at exactly the right moment.

​
How it works

1

Configure your client

Add the AmDital MCP server URL and your workspace bearer token to your client config (Claude Desktop, Cursor, etc.).
2

Client discovers tools

On connection, the MCP client sends tools/list — AmDital returns the 6 CRM tools with name, description, and typed input schema.
3

AI invokes tools

When you ask the AI to “list my leads” or “update this deal”, it calls the appropriate MCP tool (tools/call) with validated arguments.
4

AmDital responds

The server forwards the call to your workspace’s CRM data, scoped to your workspace only, and returns a typed result. The AI uses the output to continue the conversation.

Installation guide

Tool reference

Learn more about MCP at modelcontextprotocol.io.