Set Up the 6sense MCP in ChatGPT

  • Updated on Sep 3, 2026
  • Published on Jul 6, 2026
  • 4 minute(s) read
Prev Next

This article explains how to connect ChatGPT to the 6sense MCP server and authorize access.

The 6sense MCP connector is available through the OpenAI connector registry. For new connections, use the registry listing whenever available. Existing custom connector installations continue to work and do not require migration. Switching to the registry connector is optional.

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 from the OpenAI connector registry (Recommended)

The 6sense MCP connector is available through the OpenAI connector registry.

For new connections, use the registry listing whenever available. Existing custom connector installations continue to work and do not require migration. Switching to the registry connector is optional.

  1. Open ChatGPT.

  2. Open the Plugins Directory.

  3. Search the 6sense plugin.

  4. Open the plugin details.

  5. Select Install plugin.

  6. Complete the authentication flow.

  7. Sign in to 6sense when prompted.

  8. Review the requested permissions.

  9. Select Allow access to complete the connection.

For more details, see ChatGPT documentation.

Alternative: Connect using a custom connector

For new connections, the OpenAI connector registry is the recommended setup method. The custom connector option remains available for customers who prefer that workflow or already use an existing custom connector. Existing custom connector installations do not need to be migrated.

To connect to the 6sense MCP server in ChatGPT using a custom connector follow the below procedure:

  1. Enable developer mode. To turn on developer mode, navigate to Settings → Apps & Connectors → Advanced settings.

  2. Enable the toggle to turn on the developer mode.

  3. Navigate to Settings → Connectors → Create

  4. Provide connector details, including:

    1. Connector name, for example, 6sense MCP

    2. Description.

    3. Connector 6sense MCP server endpoint. Your 6sense MCP endpoint https://api.6sense.com/mcp.

    4. Choose Authentication as OAuth.

  5. Click Create.

  6. If you are not signed in, you are prompted to log in to 6sense

  7. If you are already signed in, you are shown a permissions screen

  8. You must select Allow access to complete the connection

If the connection succeeds, you will see the tools available from the MCP server.

For more details, see ChatGPT documentation.

Verify the connection

After creating the connector:

  1. Open a new chat in ChatGPT

  2. Select the + button near the message composer

  3. Select More

  4. Choose 6sense MCP connector from the list of available tools.

  5. 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:

  1. Add the 6sense MCP server in your AI assistant.

  2. Complete the authentication and authorization process.

  3. Use the AI assistant to access 6sense data through MCP.

FAQ

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:

  1. Create a separate MCP connector for each instance.

  2. Use the same 6sense MCP server URL for each connector.

  3. 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.

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.

Related articles