01
A deal the vendor server can already read
HubSpot deals, Salesforce opportunities and Pipedrive deals. All three vendors ship an MCP server. All three can also write. The question does not use the write.
CRM sales questions an agent may answer are the ones a seller already sees: open deals, the owner, the next date, the last activity. HubSpot hides activities on its MCP server when sensitive data is on. Salesforce refuses a service account. Pipedrive can update a deal, and the signed list still does not.
Two different jobs
One question, three shapes
01
HubSpot deals, Salesforce opportunities and Pipedrive deals. All three vendors ship an MCP server. All three can also write. The question does not use the write.
02
SuperOffice calls it a Sale and can return the next due date and the stakeholders. Sugar and Sage call it an Opportunity, and Sage still filters by territory. weclapp has opportunities on API v2.
03
CAS lists types per database. Opportunities are a module, not a promise of Standard Edition. cobra has no fixed opportunity URL: an admin creates the endpoint, or the question has no read.
Use cases
| Question | Where it lives | Agent |
|---|---|---|
| Which deals are mine and open? | HubSpot, Salesforce, Pipedrive, SuperOffice, Sugar, Sage | Read, as that user |
| Who else is on this account? | HubSpot contacts, Salesforce contacts, SuperOffice stakeholders | Read the people already linked |
| What happens next? | SuperOffice next due date. Pipedrive activities. HubSpot activities unless sensitive data blocks them | Read the date. Do not book the meeting |
| What did we last say to them? | HubSpot activities, Sage communications, Sugar meetings | Read, and say when the product hides the history |
| Move it to the next stage | A write on every one of these APIs | No tool |
Vendor pages read 6 October 2026. CAS and cobra are absent from the first row on purpose: the type or the endpoint has to be confirmed on that installation.
Dynamics 365 on this site is Finance, Supply Chain and Business Central. A sales question pointed at that server is the wrong catalogue.
Policy, not a live call
The allow line is the question. The deny line is the edit the model will otherwise offer to make.
caller: the seller who asked
allow: my_open_deals, owner, next_date
deny: update_stage, send_mailnext_date is omitted when the installation has no such field. An omitted field is a result.
When a chatbot inside the CRM is enough
If the seller never leaves HubSpot, Salesforce or Pipedrive, the vendor server is the shorter path. Build the read when the same question is being copied into a forecast sheet. Start from the CRM MCP server overview, then the product you actually run.
Which of my open deals close this month, and who owns each one. Every CRM in this set can hold that question once a read exists: HubSpot deals, Salesforce opportunities, Pipedrive deals, SuperOffice sales, Sugar and Sage opportunities. CAS and cobra only after the installation lists that type or that endpoint.
Only where that history is actually available to the user. HubSpot blocks calls, emails, meetings, notes and tasks on its MCP server when sensitive data is turned on. The CRM API can still have them. An answer that skips that check will say there is no history.
No. HubSpot, Salesforce and Pipedrive can write from their own servers. SuperOffice, Sugar, Sage and weclapp can write from their APIs. The question is a read. The stage change is a click the seller makes.
A two-week Readiness Blueprint at €4,900 net. We bring two users, not an administrator, and we see which of the three questions return different rows. A first production server is usually a pilot from €15,000.
Next step
Two weeks. We map each question to a documented read, or we say the installation does not have one.