Quantum Metric and Heap announced new access to customer analytics through the Model Context Protocol on Oct. 22, extending product and customer-experience data into compatible AI tools. The releases give enterprise teams another route to investigate digital behavior without beginning each question inside a vendor dashboard.
This Rapid News Brief distinguishes the two companies’ announced capabilities. Their product descriptions are not independent evidence of improved commercial results.
Quantum Metric extends its agent tool layer
In its general-availability announcement, Quantum Metric said customers can connect compatible agents to a set of 46 tools. The company describes functions including data queries, session summaries, funnel construction and monitoring.
Its stated uses include investigating incidents, evaluating product features and deciding which customer-experience changes to test. The offering includes OAuth authentication and access scoped by subscription, according to Quantum Metric. That makes the applicable subscription part of the access boundary, rather than suggesting every connected assistant receives unrestricted platform access.
Heap specifies a read-only boundary
Heap’s separate announcement says its MCP connection lets an assistant request analyses of a customer’s Heap project. Users sign in with their Heap account and approve access.
The company explicitly describes the connection as read-only: it cannot create, edit or delete items in the project. Heap says returned information consists of aggregated data and metadata, excluding names, email addresses and other personal identifiers.
Heap also identifies limits. Its initial release uses preset date ranges, while custom ranges remain on its roadmap. Saved charts, dashboards and session replays are not included. Those exclusions distinguish a fresh analytical query from full access to everything a user might see inside the product.
The operational distinction is access, not just conversation
For enterprise teams, these announcements concern where analysis can happen and which evidence an agent can retrieve. A conversational interface does not make the underlying permissions or product limits interchangeable. The documented boundaries matter when deciding whether a workflow needs aggregate usage figures, individual-session evidence or authority to make changes.