01Layer 3 · CPQ
DealHub announces “MCP for Admin” by press release. The developer docs haven’t moved.
DealHub’s 9 September 2026 release, “DealHub MCP Brings Agentic Control to Quote-to-Revenue,” introduces “MCP for Admin”: natural-language, agentic configuration of pricing rules, approval workflows and guided-selling flows, stated as “available to all customers in October 2026.” The release publishes no authentication method, scopes or tool schema. DealHub’s developer docs are unchanged since our last check: the only new agent-facing addition is a pointer to an llms.txt index of the existing REST/OpenAPI surface, a machine-readability aid, not an MCP endpoint. The third-party-only connectors we found last time (Zapier’s MCP wrapper, chiefly) are unaffected.
Why it matters: DealHub is the third vendor in three weeks to run this exact play: announce before you document. Zilliant took roughly seven months from its own version of this release to a live docs page; CaptivateIQ’s “Coming Soon” MCP page is still exactly that, unchanged since we flagged it a week ago. DealHub’s advantage over both is a checkable date — October 2026, stated by the vendor itself — so this is a short clock, not an open one. Until it resolves, anything you build against DealHub today is built against the REST/OpenAPI surface that exists now, not the agentic admin layer the release describes; budget the build accordingly and don’t roadmap around October until there’s a docs page to point at.
Source: DealHub press release (GlobeNewswire) · DealHub developer docs
02Layer 9 · CRM and Pipeline
Pipedrive ships a meeting copilot. It isn’t the agent interface some coverage implies.
Pipedrive’s own newsroom confirms Nova, a meeting-intelligence feature, went generally available on 16 September 2026: it briefs a rep before a call from logged CRM context, records and transcribes the meeting, then drafts the resulting CRM updates for the rep to “review, edit and approve.” Pipedrive describes it as operating “within the platform’s infrastructure without requiring a separate AI tool to deploy or manage,” built into the core product and included on every plan at no extra cost. There is no separate authentication flow, external endpoint or agent-facing documentation for it: Nova’s writes go through the in-product approval step, not through Pipedrive’s existing first-party MCP server or REST API, both of which are unchanged by this launch.
Why it matters: Pipedrive’s registry status is unaffected: the MCP server we already count as “Official” is a separate, distinct thing from Nova. But Nova is exactly the kind of launch this site exists to keep separate from the interfaces it tracks. It’s a genuinely useful, human-in-the-loop copilot, and it will show up in roundups this quarter as “Pipedrive ships AI agent for sales calls.” If your evaluation criteria conflate a vendor shipping an AI feature with a vendor shipping a documented agent interface an external system can call, a launch like this is exactly what gets miscounted, and the gap only shows up later, when you go looking for the endpoint and find an in-app review screen instead.
Source: Pipedrive newsroom: Nova launch