ESC
↑↓ navigate↵ open

Home / Signal / #004

Signal #004 · 28 September 2026

HubSpot's connector starts writing outside the CRM. Ahoy's already was.

Signal is a weekly note on what actually changed in the commercial software stack (pricing models, agent interfaces, ownership) tagged to the layer of the Agentic Commercial Model it belongs to. A link to the document behind every claim, and no filler to hit a quota: this issue is three items, because three is what the documentation actually supports.

Checked against the 21 September 2026 Agent Access Registry baseline: all 43 vendors' developer documentation, changelogs, GitHub repos and official press pages re-verified against that dated row.

In this issue

  1. HubSpot's Claude connector learns to write outside the CRM. Ahoy's could all along — its docs never said so.
  2. Clari's write-back MCP server was pulled from release notes in July. We only found out this week.
  3. FreshBooks ships a Claude connector and writes down, in its own docs, everything it can't do yet.
01Layer 9 · CRM and Pipeline

HubSpot's Claude connector learns to write outside the CRM. Ahoy's could all along — its docs never said so.

A Sep 15, 2026 update to HubSpot's first-party MCP server, distributed through Claude's connector directory as the “HubSpot connector for Claude,” expands documented write access well past the CRM objects and engagements we counted in August: it now covers drafting and publishing blog posts and landing pages in Marketing, logging notes on tickets in Service, and creating pipelines and custom properties in RevOps, on top of the existing deal and contact writes in Sales. HubSpot caps bulk writes at ten records per call and recommends, without requiring, an approval step before anything executes; permissioning is described at the connector and data-category level rather than as a public, per-object scope list. Separately, a correction: Ahoy's own changelog shows a one-click “Add to Claude” button for its MCP server going live Aug 13, 2026, and its July “Introducing Ahoy” post already described shipping “open by design, with an MCP server, webhooks, and team API keys.” We had Ahoy down as “none found” in August; that was wrong. We still can't find a developer portal, API reference, or a single documented auth method or scope for it, so it moves to “claimed, undocumented” — the same shelf as ChurnZero and Highspot, not back to zero.

Why it matters: If you built against HubSpot's connector in August, its write scope just got materially larger, and materially less specific about exactly what it's allowed to touch; re-test before you extend what you let it do unattended, and don't assume category-level permissioning catches what an object-level scope list would. The Ahoy correction is as much about our own method as about Ahoy: a live “connect to Claude” button is not documentation, and a vendor with a real interface and zero developer docs is the same evaluation problem as a vendor with a “coming soon” page. If your own vendor scorecard counts a connector-directory listing as proof of an agent interface, you're measuring the wrong thing.

Source: HubSpot: connector for Claude · HubSpot community: MCP server updates · Ahoy: what's new · Ahoy: Introducing Ahoy

02Layer 4 · Sales Enablement and Revenue Intelligence

Clari's write-back MCP server was pulled from release notes in July. We only found out this week.

Clari and Salesloft have completed their merger and now operate as one company under the Salesloft brand, per Salesloft's own merger page. That bears on the Clari + Salesloft MCP server our August entry flagged as the vendor's answer to write-back: Clari's community forum shows the underlying “Copilot MCP Server” was quietly pulled from Clari's own July 2026 release notes, with a Clari staff member telling a customer on Jul 14, 2026 that the team “wanted more time to make sure it holds up against real customer use cases” before it went out to everyone, and giving no new date. Clari's dedicated developer docs still show only the plain REST export-jobs spec we found in August: no MCP, no Salesloft, no write-back.

Why it matters: the “late summer 2026” window in our own August note came from a Salesloft help-centre reference that was already stale by the time we wrote it down; the retraction happened weeks earlier, in a forum reply, not a changelog or a press update. That's the pattern this column keeps finding, just running the other direction this time: the gap between documented and true isn't only a vendor overclaiming a launch date, it can also be a walked-back promise nobody bothered to un-announce. If you're evaluating Clari, or the merged Clari/Salesloft entity, for write-back today, plan around a read-only relationship until there's an actual docs page, not a forecast.

Source: Clari community: Copilot MCP Server · Clari developer docs

03Finance and Operations · Accounting

FreshBooks ships a Claude connector and writes down, in its own docs, everything it can't do yet.

FreshBooks announced a first-party MCP-based connector for Claude on Sep 25, 2026, and its own support article is unusually specific about the boundary: the connector is “currently read only and can only read your live data to answer questions, not change data,” covering profit and loss, invoicing, expenses, estimates and client records. Write actions — creating, editing or deleting invoices, expenses, clients, projects and journal entries — are listed as “coming soon,” with an opt-in toggle so users can enable them later without reconnecting. FreshBooks' existing, separately documented REST API already supports full create/read/update/delete writes under its own auth, unaffected by this launch.

Why it matters: this is close to the opposite failure mode from DealHub and CaptivateIQ. Where those vendors' press releases describe a write-capable future with nothing in the docs, FreshBooks documents a read-only present and states the write scope isn't live yet, in the same article, in writing. That's a low bar, and it's still worth naming when a vendor clears it: if your evaluation criteria can't tell “coming soon, undocumented” from “coming soon, and the docs say so,” you'll keep grading the straightforward vendors the same as the vague ones. FreshBooks' MCP status moves to “Official” in the registry; agent write access there was already “documented” through the plain REST API and stays that way — the new connector adds a second, currently narrower way in, not new write capability.

Source: FreshBooks: connector in Claude · FreshBooks press release

Registry moves

Two rows change status, two get fuller notes, and one sheds a beta label; all five re-dated to 28 September 2026. FreshBooks moves from “Third party only” to “Official” following its Sep 25 Claude connector launch (read only today; agent write access there stays documented independently through its existing REST API). Ahoy corrects from “None found” to “Claimed, undocumented”: a live “Add to Claude” button for its MCP server has been in the changelog since Aug 13, with no developer documentation behind it anywhere we could find. HubSpot's and Clari's notes are updated without a tier change — HubSpot's to record its expanded, less granularly scoped write access across Marketing, Service and RevOps; Clari's to record its Copilot MCP Server's undated pull from July's release notes and the completed Salesloft merger. Separately, ClickFunnels' MCP server drops its “beta” label: docs updated Sep 16, 2026 describe a new production endpoint (agents.myclickfunnels.com/mcp) with the prior technical-preview endpoint retained as legacy.

One aggregate figure moves: the registry now shows 26 of 43 vendors publishing an official MCP server, up from 25. The write-access figure (31 of 43) and the single zero-interface category (Sales Compensation & Incentive Management) are unchanged.

Signal lands weekly. The registry updates with it.

Layer tagged, evidence linked. If something here is wrong or out of date, tell us and we will re check and re date the row.

Open the registry →