What is 6sense MCP?
6sense MCP is an MCP-compatible integration layer that allows AI assistants to retrieve selected 6sense insights through natural-language queries.
What can I do with MCP?
You can use MCP to:
retrieve account summaries
search for people associated with accounts
analyze 6QA trends
enrich people information
review keyword activity
evaluate campaign performance
retrieve sales insights and recent company news
unlock available contact information using Sales Intelligence credits
What data does MCP use?
MCP retrieves data from your 6sense environment through Revvy AI subagents.
Does MCP provide access to all 6sense data?
No. MCP currently retrieves data only through Revvy AI subagents and does not provide access to all 6sense data.
Who can use MCP?
MCP capabilities depend on your organization’s 6sense licenses and your assigned user role.
Users with Revenue Marketing access can use the marketing capabilities available for their license and role. Users with Sales Intelligence access can use supported sales-focused capabilities, including detailed account summaries.
Do I need to authenticate to use MCP?
Yes. Each user must connect and authorize access individually.
Is access shared across users?
No. Each user must authorize access separately.
Does MCP modify 6sense data?
No. The current release is read-only.
Do I need to select tools when using MCP?
No. The AI assistant selects tools automatically based on the query.
How that data is handled, stored, or retained is determined by the AI assistant platform you use?
6sense MCP retrieves data from your 6sense account and sends it to the connected AI assistant after you authorize access. How that data is handled, stored, or retained is determined by the AI assistant platform you use.
Do all AI assistants work the same way with MCP?
No. Each AI assistant provides a different connection experience, even though they use the same underlying MCP protocol.
Why does MCP return a different answer than Revvy AI for the same question?
MCP uses the same underlying Revvy AI capabilities, but responses may differ because AI assistants interpret and present information differently. In addition, MCP supports a read-only subset of Revvy AI capabilities, and AI-generated responses are not deterministic. As a result, the same question can produce different responses across platforms or across multiple attempts.
Can I connect the same AI assistant to multiple 6sense instances?
Yes. You can create multiple MCP connector instances and authorize each connector against a different 6sense instance. For example, a consultant or agency user who has access to multiple customer instances can:
Create a separate MCP connector for each instance.
Use the same 6sense MCP server URL for each connector.
Authorize each connector using credentials for the appropriate 6sense instance.
In ChatGPT, this can be done by creating multiple custom connectors with different names, such as:
6sense – Customer A
6sense – Customer B
Important considerations:
You must have valid credentials and access to each 6sense instance.
Each connector must be authorized separately.
Switching between instances may require reconnecting or selecting the appropriate connector, depending on the AI platform.
The AI assistant does not automatically understand which 6sense instance you want to query. You may need to use separate connectors or clearly identify the instance in your workflow.
Example: An agency supporting multiple customers can create separate MCP connectors for each customer environment and authorize each connector independently.
Data isolation
Each connector is independently authorized and scoped to the 6sense instance used during authentication.
Data is not shared between connectors.
Authorizing multiple connectors does not combine or commingle data across instances.
Queries return data only from the instance associated with the selected connector.
For example, if you create separate connectors for Customer A and Customer B, data retrieved through the Customer A connector is limited to Customer A's 6sense instance, and data retrieved through the Customer B connector is limited to Customer B's 6sense instance.
Can MCP provide website activity at the contact level?
It depends on the customer's license and role.
Revenue Marketing capabilities provide account-level website activity insights. Users with Sales Intelligence access can use supported sales-focused capabilities to retrieve engagement information for known contacts. Contact-level activity is limited to known CRM records and does not de-anonymize anonymous visitors.
Can I unlock contacts through MCP?
Yes. Users with the required Sales Intelligence access and permissions can unlock contact information through MCP using their existing credit allocation. Contact unlock works the same way as it does in Sales Intelligence.