MCP for CRM work: let Claude fetch the ticket instead of pasting it
How the Model Context Protocol lets Claude read CRM and ticket data directly, what tools, resources and prompts mean, and the safety rules I keep.
A lot of AI work in CRM is copy and paste: open the ticket, copy the history, paste it into the chat, ask the question. The Model Context Protocol (MCP) removes that step. Claude asks a server for what it needs, with the permissions you gave it.
Before and after
Copy and paste
- Agent copies the ticket into the chat
- Context is whatever was pasted
- Customer data spreads into chat logs
- Every person does it differently
With an MCP server
- Claude requests ticket #18422
- Context is the full, current record
- Data stays behind the server's rules
- One server, one way, for the whole team
The three building blocks
Toolsactions, such as creating a ticket note
Resourcesread-only data, such as a contact record
Promptsreusable instructions, such as "summarise this account"
The order I add things
01Readresources only: tickets, contacts, history
02SuggestClaude drafts notes for a person to save
03Actnarrow tools, one at a time, each logged
04Reviewweekly look at what the tools actually did
Rules that stay on
Read-only firstno write tools until the reads are trusted
Least accessthe server sees only the objects it needs
Test in the inspectorbefore Claude ever calls a tool
Log every callso the QA sample covers tool use too