6sense Revenue Marketing is included for its vendor-hosted, per-user OAuth MCP that gives AI clients read-only access to Revvy AI-supported account intelligence, campaign and website signals, segments, and 6sense product knowledge.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Accounts and their activity or buying signals, 6QA trends, keyword and ad-campaign performance, website activity, eligible segments and deep links, market research context, and 6sense product-support knowledge within Revvy AI-supported scenarios.
Retrieve and summarize Revvy AI-supported 6sense context for account research, signal and trend analysis, campaign or website performance, segment discovery, and product support.
No MCP write scope is documented in the current beta. 6sense explicitly describes the service as read-only and says it does not execute actions or modify 6sense data.
The hosted MCP uses per-user OAuth authorization and requires a 6sense Revenue Marketing account and organization; each user connects independently.
Access is user-specific and read-only, while data handling, storage, and retention in the connected AI assistant are governed by that external client. 6sense also cautions that phrasing can produce different results.
Beta; limited to Revvy AI-supported scenarios rather than all 6sense data; company and contact enrichment are unavailable; standard Microsoft Copilot is unsupported; Revenue Marketing entitlement is required.
First-party access
Agent access
Support: Official MCP server
Read scope: Read account activity and buying signals, 6QA trends, keyword and campaign performance, website activity, eligible segments, market research, and product-support answers exposed through Revvy AI scenarios.
Write scope: None in the documented beta: the 6sense MCP is read-only and cannot execute actions or modify platform data.
Authentication: Per-user OAuth to the vendor-hosted 6sense endpoint; every user authorizes their own Revenue Marketing account connection.
Approval boundary: No mutation approval is needed for the documented read-only tools. A BYO-UI should still show the selected account, time range, and external AI client before retrieval because query phrasing and client-side retention can change the practical result and exposure.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that 6sense ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
beta maturity, Revvy AI-supported reads, prohibited writes, unavailable enrichment, and client data handling
Beta scope, read-only behavior, scenario catalog, and limits reviewed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Official 6sense docs published July 6, 2026 confirm beta and account/organization prerequisites; original source URL should be updated.
Targeted first-party MCP/agent-role review; broader API inventory retained
6sense MCP client compatibility
6sense MCP client compatibility reviewed from live first-party material on 2026-07-22.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
