Key takeaways
- MCP lets an assistant use another tool's actions with your own sign-in.
- Think in rep jobs, such as call prep and call follow-up, not in tool names.
- MCP acts on request in a conversation; it is not a background sync.
- Check what each server can change and how approvals work before connecting it.
What is MCP in plain words for sales
MCP, the Model Context Protocol, is an open standard that lets an AI assistant call another tool's actions, usually through your own sign-in to that tool. The tool decides which actions it offers, and the assistant only sees what your account can see.
For a rep, the practical effect is fewer tabs. Instead of opening the CRM, the billing tool and the scheduling tool in turn, you ask one assistant a question and it looks in the right place.
Which jobs do MCP servers for sales help with
MCP servers help most with the small lookups and updates around a conversation, the jobs reps often skip when they are busy. Grouped by moment in the day, they look like this.
- Before a call: pull the account's CRM record, open deals and last notes into one summary.
- After a call: write the summary and agreed next step back to the CRM record.
- Before a renewal or upsell: check the customer's plan and billing status.
- When booking: find the right booking link or event type to send.
- When a technical question comes in: look up the issue or the internal page before replying.
- Before writing to a contact: check whether they already sit in a sequence in another tool.
How is MCP for sales reps different from an integration
A typical integration moves data between two tools on a schedule; MCP lets an assistant act on request, inside a conversation. Nothing runs in the background, and each call happens because someone asked.
That cuts both ways. Records change only when a rep asks, and approval can sit in front of each write, which suits teams wary of automatic writes. It also means nothing stays in step by itself, so the habit of asking the assistant to update the record after each call is what keeps the CRM current.
What should reps check before connecting a sales tool
Check what the server can change, whose permissions it uses and how approvals work, before the first connection. These three answers decide how much you can trust it with.
- Which actions the server exposes, and which of them write or delete.
- Which writes wait for your approval, and in which modes.
- Whether your account sees more than you want the assistant to use.
- What disconnecting does, and whether you also need to revoke access at the provider.
Where Pebbles Ai fits
- FoundationIntegrationsAny user can connect MCP servers from the Pebbles Ai catalogue, such as Attio, Pipedrive, Stripe, Calendly, Atlassian and Apollo.io, each with the service's own sign-in; the catalogue may change. Disconnecting removes the stored credentials in Pebbles Ai but does not revoke the grant at the provider.
- CapabilityAI workspaceThe Marketing and Strategy assistants use MCP tools, and every MCP call follows the execution mode: it asks for approval in Manual, is queued in Plan and runs without asking in Auto.
Common questions
Do I need to write code to use MCP?
No. In Pebbles Ai you connect a catalogue server from Settings, Connections, with that service's own sign-in, and then ask the assistant in plain words.
Can MCP keep my CRM in sync automatically?
Not in Pebbles Ai. The assistants keep Attio or Pipedrive in step by reading and writing records when you ask, each write an approval action under your execution mode; there is no background or two-way sync.
Can I add any MCP server I like?
Pebbles Ai connects servers from its own catalogue only, not by URL. HubSpot and Salesforce are not in the catalogue.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
