Key takeaways
- Sales operations owns the register of approved servers and the rules; each rep owns their own sign-in.
- Choose a route per tool: the vendor's own server, a general assistant's connector or a workspace catalogue.
- Write approval rules per type of action before anyone moves a team workflow to an automatic mode.
- Offboarding has two steps: disconnect in the assistant and revoke the grant at the provider.
Why does MCP become a team decision in 2027
It becomes a team decision because MCP has moved from a connection one rep tries to a layer several people and several vendors rely on. Apollo.io describes Apollo Anywhere, which brings its data into tools such as ChatGPT and Claude with an MCP server and API; Salesloft lists MCP among its products; and Lusha lists MCP beside its browser extension, CRM integrations and API.
Once several people connect several servers, the open questions are about control: who may write to the CRM through an assistant, which actions wait for a person and what happens to a connection when a rep leaves. This page covers that team rollout; what MCP is and the jobs one rep uses it for are in the evergreen guide on how sales reps use MCP.
Which route should a sales team choose for each tool
Choose per tool, by where the team already works and who needs to control the permissions. Most teams end up with more than one route, which is why the register below matters.
- The vendor's own server: Apollo.io and Lusha both describe MCP access to their data, which suits a team that lives in that tool already.
- A general assistant: ChatGPT works with outside services through apps built on MCP, and admins choose who can use each app and whether it may read or also change information; Claude offers connectors, including interactive MCP apps.
- A workspace catalogue: Pebbles Ai, an AI workspace whose assistants research accounts with cited sources, find fresh leads with work emails and write outreach and social posts from your company knowledge, connects servers from its own catalogue, such as Attio, Pipedrive, Apollo.io, Outreach, Calendly, Stripe and Atlassian, each call under the execution mode, with each service's own sign-in; the catalogue may change.
- An agent product: Lindy lists MCP support among the integrations of its general work agent.
- No MCP: scheduled integrations between tools, for a team that wants no assistant writing to its systems.
What goes in the team's MCP register
The register lists each approved server with the jobs it serves, the actions that write or delete, the approval rule for each, the owner and the date it was last reviewed. A short table is enough, kept where every rep can read it.
Review it when a vendor changes what its server can do, when a new tool joins the stack and when someone changes role, because a renewals manager and an account executive rarely need the same servers.
How should a team set approval rules for MCP writes
Set them by risk: reads can run freely, writes to shared records should wait for a person at first, and deletes should almost always wait. Relax a rule only after the team has watched the assistant handle that write correctly many times.
Write the rule in the words reps use, such as deal stage changes need approval but notes do not, and match each assistant's settings to it. If assistant writes start allocating leads or accounts between reps, check California's automated decision rules from 1 January 2027 and, in the EU, whether the high-risk duties from 2 December 2027 apply to AI that allocates tasks to staff by their behaviour or traits. This is not legal advice.
How does a sales team run MCP in Pebbles Ai
In Pebbles Ai each person connects the approved servers from the catalogue with their own sign-in, and every MCP call follows the execution mode that person picks, so the same assistants that research accounts and write outreach can read and update Attio or Pipedrive from the conversation.
- Sales operations shares the approved list; each rep opens Settings, Connections and connects only those servers, with the service's own sign-in.
- The team agrees a default execution mode: in Manual every MCP call waits on an approval card, in Plan it is queued, and in Auto it runs without asking.
- The pilot group asks the Marketing or Strategy assistant for team jobs in plain words, such as a summary of an Attio account before a pipeline review.
- Writes to Attio or Pipedrive happen from the conversation, each an approval action under the execution mode.
- A team that would rather not connect an outside CRM can keep deals in the Pebbles Ai CRM beside the assistants.
- When someone leaves, disconnect their servers in Pebbles Ai, which removes the stored credentials, and revoke the grant at each provider as well.
Roll MCP out from a pilot group to the whole team
Plan the rollout like any change to a system of record: small first, written down and reviewed.
- Name the owner of the register, usually sales operations or RevOps.
- Pick two or three team workflows, such as pipeline review preparation or renewal checks, and the servers they need.
- Choose the route for each tool and record it in the register with the actions that write or delete.
- Write the approval rule for each write and delete, and decide who may move a workflow to an automatic mode.
- Give a pilot group two weeks with their own sign-ins, then inspect every record the assistants changed.
- Roll out to the rest of the team with the register, the rules and one worked example per workflow.
- Add both offboarding steps to the leaver checklist, and review the register each quarter.
Where Pebbles Ai fits
- FoundationIntegrationsAny user connects MCP servers from the Pebbles Ai catalogue with the service's own sign-in, so each rep's access is their own; servers come from that catalogue, which may change. Disconnect removes stored credentials in Pebbles Ai; revoke the grant at the provider as well.
- CapabilityAI workspaceThe Marketing and Strategy assistants use MCP tools, and every MCP call follows the execution mode: approval in Manual, queued in Plan, run without asking in Auto.
- CapabilityProspecting & customer recordsTeams that would rather not connect an outside CRM can keep deals in the Pebbles Ai CRM beside the assistants.
Common questions
Is MCP safe for a sales team to use with its CRM in 2027?
It can be, if each person signs in with their own account, writes wait for approval until the team trusts them and offboarding revokes access at the provider. Safety comes from those rules, not from the protocol alone.
Can HubSpot or Salesforce connect to Pebbles Ai through MCP?
The CRMs in the Pebbles Ai catalogue today are Attio and Pipedrive, connected through MCP with each write under your execution mode, and the catalogue may change. A HubSpot or Salesforce team can import contacts from a CSV straight into segments of the Pebbles Ai CRM.
Should every rep connect the same MCP servers?
Not necessarily. Connect the servers each role's jobs need: an account executive may need the CRM and scheduling, a renewals manager the CRM and billing.
Who should review a sales team's MCP register in 2027?
Its owner, usually in sales operations or RevOps, with a security reviewer for any server that can write or delete. Review it each quarter and whenever a vendor changes what its server can do.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .