6sense opens MCP Server beta to Revenue Marketing customers
6sense released its MCP Server in open beta for Revenue Marketing customers, with general availability planned for August 2026.
6sense launched its Model Context Protocol (MCP) Server in open beta on July 14, 2026 for Revenue Marketing customers. The server makes account insights, predictive buying stages, 6sense Qualified Account (6QA) status, keyword intent and ad campaign performance callable from MCP-compatible agents without custom integration, naming Claude, ChatGPT, Writer and Agentforce. Retrievals run through RevvyAI and return in plain language. 6sense said general availability was planned for August 2026.
The details
- Company and contact enrichment and deeper coverage are planned for later releases.
- Each 6QA comes with the reasoning behind it, including which inputs moved the score and how it compares to past outcomes.
- 6sense says its Signalverse network was built over 13 years and spans more than 200,000 B2B properties.
- The company reports that, from Q2 2025 to Q1 2026, opportunities on 6QA accounts carried 29% higher values for its predictive customers.
- 6sense says the server requires no custom integration on the agent side.
Context
RevvyAI, which powers the server, was opened to all 6sense customers in May 2026 along with enterprise security controls. destinationCRM covered the MCP launch the following day. On August 10, 6sense announced the MCP Server again as part of four releases that also included people data updates and new data APIs, which correspond to the enrichment work flagged here as planned. The company named Micki Howl chief revenue officer on July 8.
Not disclosed
- Pricing
- Whether beta access extends beyond Revenue Marketing customers
- Vendor
6sense- Category
- ABM Platforms
- Announcement type
- AI launch
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.





