This article explains how to connect Claude to the 6sense MCP server and authorize access.
The 6sense MCP connector is available through the Claude connector catalog. For new connections, use the catalog listing whenever available. Existing custom connector installations continue to work and do not require migration.
Before you begin
Before you set up MCP:
You must have access to a 6sense account.
Your organization must have access to the Revenue Marketing platform.
Each user must authorize access individually.
Admin rights in your AI agent platform, if your organization requires an administrator to register connectors.
Authorization
Authorization is required when you connect to the 6sense MCP server.
How authorization works
If you are not signed in, you are prompted to log in to 6sense
If you are already signed in, you are shown a permissions screen
You must select Allow access to complete the connection
Important
Authorization is required per user
Each user must authorize access individually
Authorization is required even if advanced settings are used
Connect through the Claude connector catalog (Recommended)
Open Claude.
Go to Settings > Connectors > Browse.
Search for 6sense.
Select the 6sense connector.
Review the connector information.
Select Connect.
Follow the authentication prompts to grant Claude access to your account.
Configure any permissions requested during setup.
When prompted by 6sense:
Sign in to your 6sense account.
Review the requested permissions.
Select Allow access.
You can also access the 6sense connector directly from the Claude connector catalog using https://claude.ai/directory/connectors/6sense.
For more details, see Claude documentation.
Alternative: Connect using a custom connector
For new connections, the catalog listing is the recommended setup method. The custom connector option remains available for customers who prefer that workflow or already use an existing custom connector.
In Claude:
Go to Settings or your organization’s settings
Select Connectors
Select + Add custom connector
Provide the connector details:
Connector name — for example, 6sense MCP
MCP server URL — your 6sense MCP endpoint https://api.6sense.com/mcp
Select Connect or Authorize.
If you are not signed in, you are prompted to log in to 6sense
If you are already signed in, you are shown a permissions screen
You must select Allow access to complete the connection
For more details, see Claude documentation.
Verify the connection
After connecting the 6sense MCP server, ask a question that requires 6sense data. For example, “Using 6sense, what is the current buying stage and top intent keywords for salesforce.com?”
If the connection works, your AI assistant:
The AI assistant invokes a 6sense tool.
The response includes 6sense account data.
Information such as buying stage, intent topics, or account details is returned.
If the connection doesn’t work, your AI assistant:
Provides only general knowledge responses
Indicates that no tool is available
Cannot retrieve 6sense data
To troubleshoot the issue, verify that:
The connector has been added.
The connection has been authorized.
The connector is enabled for the conversation or agent.
Troubleshooting
Unauthorized error (401) when opening the MCP URL in a browser
Symptoms
When you open the 6sense MCP server URL directly in a browser, you see an error similar to: Your API token is invalid or auth token is invalid or missing authorization header.
You may also see a 401 Unauthorized error.
Cause
This behavior is expected.
The 6sense MCP server is not intended to be accessed directly through a web browser. MCP connections are initiated and authenticated through a supported AI assistant, such as Claude, ChatGPT, or Microsoft Copilot Studio.
When you navigate to the MCP endpoint directly, the request does not contain the required authentication information, and the MCP server returns a 401 Unauthorized response.
Resolution
Do not open the MCP server URL directly in a browser.
Instead:
Add the 6sense MCP server in your AI assistant.
Complete the authentication and authorization process.
Use the AI assistant to access 6sense data through MCP.
FAQ
Does the catalog listing replace the custom connector?
No. Both installation methods remain available. The catalog listing is the recommended option for new connections because it simplifies setup, but the custom connector remains supported.
Will existing users need to migrate?
No. Existing custom connector installations continue to work and do not require migration.
Does the catalog listing change data access?
No. The catalog listing changes how users discover and install the connector, not what data or capabilities they can access. Access continues to be governed by beta enrollment and organization-level settings.