ESC
↑↓ navigate↵ open

Home / Signal / #006

Signal #006 · 12 October 2026

Gusto's MCP server learns to serve the accountant, not just the employer. Sierra and Meta propose one protocol for every agent.

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 5 October 2026 Agent Access Registry baseline: all 43 vendors' developer documentation, changelogs, GitHub repos and official press pages re-verified against that dated row. No vendor's MCP, API or write-access status moved this week, so the registry itself is unchanged.

In this issue

  1. Gusto's MCP server learns to serve the accountant managing many clients, not just one employer.
  2. Sierra and Meta propose a shared protocol for consumer agents to transact with any business. The spec itself isn’t out yet.
  3. Clari's write-back MCP isn’t one server. It's two, and only one has a ‘paused’ notice with its name on it.
01Finance and Operations · HR and Payroll

Gusto's MCP server learns to serve the accountant managing many clients, not just one employer.

Gusto's Oct 7, 2026 “Gusto Next” event relaunched its accountant product, Gusto Pro, adding what Gusto's own announcement calls a “multi-client Model Context Protocol (MCP)”: an accountant connects once, picks which of their client accounts an AI conversation can reach, asks cross-client questions, and can have the agent prepare payroll changes (hours, earnings, time off, payment methods) or run background weekly routines such as scanning client emails for hours. Gusto is explicit about the guardrail: “every change still comes back to the accountant to review and approve before anything is updated in Gusto.” The announcement names the capability but not the architecture: no auth method, scope list or tool names are disclosed, and it isn't stated whether multi-client access runs through the same mcp.api.gusto.com endpoint already on file in our registry or a separate one.

Why it matters: Gusto's existing employer-facing MCP server already cleared this registry's bar for a documented, write-capable interface back in September. This is a different buyer: not the company running its own payroll, but the accounting firm managing dozens of clients' payroll through one agent conversation — a genuinely new wedge for who gets to hold the agent relationship. It's also a reminder not to grade a vendor once and move on: “documented MCP server” can describe more than one surface with different scopes under the same vendor name, and a scorecard that collapses them into a single pill misses exactly the distinction this registry exists to hold onto. We're not changing Gusto's registry row this week — the architecture gap means we can't yet write a specific, checkable claim about this surface — but it's one to watch.

Source: Gusto: Introducing the new Gusto Pro · Gusto: Gusto MCP (existing employer-facing server, for comparison)

02Layer 6 + 8 · Billing and Usage Metering

Sierra and Meta propose a shared protocol for consumer agents to transact with any business. The spec itself isn’t out yet.

On Oct 6, 2026, Sierra and Meta introduced the “Personal Agent Protocol” (PAP): an open standard for how a consumer's own AI agent authenticates to a business and transacts on their behalf. Stripe and Shopify are named backers quoted directly on the announcement; Walmart, Genesys, Instinct and Rocket are listed as partners without quotes. Per Sierra's own post, a PAP session runs over OAuth, the customer (not the business) decides whether their agent gets read-only or write access, businesses separately set the parameters for what any agent can do, and a business can expose itself to PAP agents through interfaces “built on standards such as MCP and OpenAPI,” or through its own conversational agent. Sierra states a formal v0.1 spec and reference implementation are coming “later this month” — as of this issue, neither has shipped.

Why it matters: this isn't a claim about any one vendor in the registry — it's an attempt to standardize exactly the boundary this column has been checking vendor by vendor since issue #001: who authenticates, what scope they get, read or write. If PAP ships a real spec and Stripe actually builds to it, billing and usage-metering vendors would have a template for an agent interface built for an external consumer's own agent, rather than each inventing its own (right now, not one of the five vendors we track in that layer publishes anything aimed at a customer's own agent rather than the vendor's own integration partners). For now it's a blog post and a promised date, which is precisely the category this site exists to be skeptical of: DealHub's October deadline, two issues back, was also just a blog post and a promised date. We'll check back when the spec is actually out.

Source: Sierra: Introducing the Personal Agent Protocol

03Layer 4 · Sales Enablement and Revenue Intelligence

Clari's write-back MCP isn’t one server. It's two, and only one has a ‘paused’ notice with its name on it.

Our Sep 28 note described Clari's “Copilot MCP Server” — the write-back tool for its forecasting product — as quietly pulled from release notes with no new date. Rechecking this week surfaces a second, broader surface under the merged Salesloft/Clari brand: a “Salesloft MCP Server,” live since April 2026 and expanded July 9, 2026 per Salesloft's own newsroom, which states it adds “write-back capabilities, so AI tools can take action inside Salesloft and Clari” and is listed in Claude's connector directory “with no custom setup required.” That press release links to no developer portal, API reference or tool schema anywhere on the page. developer.clari.com — blocked to an automated fetch by its own robots.txt both this week and in our Sep 28 check — remains, as far as we can verify, limited to the plain REST export-jobs spec found in August.

Why it matters: these are two different claims, not one story moving forward. The forecasting-specific Copilot MCP Server is explicitly paused with no date attached. A separate, broader Salesloft MCP Server claims live write-back into Clari today, distributed through a connector directory rather than published as a vendor-run technical spec. If you're evaluating Clari for agent write access, which of the two you're being sold matters, and neither one currently clears this registry's documentation bar — which is exactly why the row stays “Unclear,” just for a sharper reason than it did in September.

Source: Salesloft: Salesloft MCP Server newsroom · Salesloft community: Copilot MCP Server removed · Clari developer docs

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 →