Connecting Thematic MCP using OAuth DCR

This page details connection instructions for common clients that require creating a bearer token, also known as 'header based authentication'.

There are three ways of connecting MCP servers:

  1. OAuth using dynamic client registration. This is the simplest and most modern. Claude, ChatGPT and Cursor all use this
  2. OAuth using explicit client registation. Gemini Enterprise requires this
  3. Bearer tokens. Needed for when you can't auth in a browser and only have terminal access.

More information about the Thematic MCP Server can be found here. If the client you use isn't listed here, you might find it in one of the other categories above.

The region to server url table is reproduced here for convenience. It is vital you use the correct region when setting up the connection to ensure you can find your organization and data after connecting.

Region

MCP Server URL
US https://mcp.client.getthematic.com   
ANZ https://mcp.client.anz.getthematic.com   
EU https://mcp.client.eu.getthematic.com   

Client specific instructions

Claude.ai

Claude.ai supports remote MCP servers natively through its Integrations settings.

  1. Go to claude.ai and sign in
  2. Click the 'Customize' button on the left panel
  3. Click 'Connectors'
  4. Click the '+' button and choose 'Custom connector'
  5. Give it a name and enter the server URL from the table above. For example https://mcp.client.getthematic.com   
  6. Click Connect — you'll be redirected to the Thematic login page
  7. Enter your Thematic email and password (or sign in via SSO)
  8. Select your organization when prompted
  9. You'll be redirected back to Claude.ai with the integration active

Once connected, start a new conversation and Thematic tools will be available automatically. You can ask questions like:

"What are the main themes in our NPS survey?"

Claude Code (CLI)

Claude Code supports remote MCP servers via its settings file.

Option 1: Add via the CLI

Run this command in your terminal:

claude mcp add thematic --transport http https://mcp.client.getthematic.com   

When you next start a Claude Code session that uses Thematic tools, you'll be prompted to authenticate in your browser.

Option 2: Add manually to settings

Add the following to your ~/.claude/settings.json    (or project-level .claude/settings.json    ):

{ "mcpServers": { "thematic": { "type": "http", "url": "https://mcp.client.getthematic.com" } } }   

Restart Claude Code after saving. You'll be prompted to authenticate on first use.

Cursor

Cursor supports remote MCP servers through its settings UI or configuration file.

Option 1: Via Settings UI

  1. Open Cursor

    Go to Settings > MCP

    Click + Add new MCP server

    Fill in:

    • Name: Thematic   
    • Type: HTTP   
    • URL: https://mcp.client.getthematic.com   
  2. Click Save
  3. You'll be prompted to authenticate in your browser on first use

Option 2: Via configuration file

Add the following to your .cursor/mcp.json    file (create it if it doesn't exist):

{ "mcpServers": { "thematic": { "type": "http", "url": "https://mcp.client.getthematic.com" } } }   

Restart Cursor after saving. You'll be prompted to authenticate on first use.

ChatGPT

ChatGPT supports remote MCP servers for Plus, Pro, and Team users.

  1. Open chatgpt.com

    Open "Settings" by clicking on the account name in the bottom left

    Chose "Apps" and then "Advanced Settings"

    Make sure "developer" mode is turned on

    Select Create app

    Enter details:

    1. Name: Thematic MCP (or similar)
    2. URL https://mcp.client.getthematic.com   
    3. Click "I understand and want to continue"
  2. Click Create — you'll be redirected to the Thematic login page
  3. Enter your Thematic credentials and select your organization
  4. Return to ChatGPT and start asking questions

Note: MCP support in ChatGPT is relatively new and may have limitations compared to Claude-based clients. If you encounter issues, try disconnecting and reconnecting the server.

Microsoft 365 Copilot

Microsoft 365 Copilot does not let individual end users connect their own MCP servers. Connecting Thematic to Microsoft 365 Copilot requires someone with Copilot Studio access (a "maker") in your tenant to build a declarative agent that wraps the Thematic MCP server, and — depending on which path your organization chooses — a tenant admin to approve it.

There are two supported paths. Pick based on how your organization governs Copilot extensibility.

In this path, a maker in your tenant creates a declarative agent in Copilot Studio that connects to Thematic, then publishes it to Microsoft 365 Copilot. End users add the agent from inside Copilot and use it like any other.

For the maker (one-time setup):

  1. Sign in to Microsoft Copilot Studio with an account that has maker permissions.

    Select Create > New agent, give it a name (e.g. Thematic Feedback Analyst) and a description, and finish creation.

    Open the agent, go to the Tools tab, and select Add a tool > New tool > Model Context Protocol.

    In the MCP onboarding wizard, fill in:

    • Server name: Thematic   
    • Server description: Analyze customer feedback in Thematic   
    • Server URL: the URL from the Server URL table at the top of this article (e.g. https://mcp.client.getthematic.com    for US)
    • Authentication: OAuth 2.0    with Dynamic discovery (Thematic supports OAuth 2.0 Dynamic Client Registration, so no manual app registration is required)
  2. Select Create, then create a new connection and sign in with your Thematic credentials when prompted.
  3. Back on the agent, ensure generative orchestration is enabled (Settings > Generative AI). MCP requires this.
  4. Test the agent in the Test pane with a prompt like "What are the top themes in our most recent NPS survey?"
  5. Select Publish, then Channels > add Teams and Microsoft 365 Copilot.
  6. Use the Share menu to grant access to the users or groups who should be able to use the agent.

For end users:

  1. Sign in to Microsoft 365 Copilot (in the browser, the Teams app, or any Copilot-enabled Office app).
  2. Open the agents panel on the left and select the agent your maker published.
  3. On first use you'll be prompted to authenticate with Thematic — sign in and select your organization.
  4. Ask questions naturally, e.g. "Compare this quarter's themes to last quarter for our NPS survey."

Option 2: Register via Bring Your Own MCP (preview, enterprise governance)

This path is the right one if your security or compliance team wants every external MCP server to go through a formal tenant-wide approval and to land in the Microsoft 365 admin center's tool registry, with all tool invocations observable in Microsoft Defender. It requires Agent 365 to be available in your tenant (included in Microsoft 365 E7, or available as an add-on).

For the developer/maker (registers the server):

  1. Install the Agent 365 CLI (version 1.1.165-preview    or greater).
  2. Confirm the Agent 365 service principal is provisioned in your tenant (appId ea9ffc3e-8a23-4a7d-836d-234d7c7565c1    ). If it's not, an admin needs to provision it first.
  3. Run the registration command, pointing at the Thematic MCP server URL for your region:
a365 develop-mcp register-external-mcp-server
--server-url https://mcp.client.getthematic.com
--name "Thematic"
--auth-type oauth2-dcr

(Or use the -f path/to/manifest.json    form if you prefer to declare the server in a JSON manifest.) 4. The registration appears in the Microsoft 365 admin center as a pending request for an admin to review.

For the admin (approves the request):

  1. Sign in to the Microsoft 365 admin center.
  2. In the left navigation, expand Show all > Agents > Tools.
  3. Open the Requests tab. The Thematic MCP server appears in the list with the requester's name, the server URL, the declared tools, and the requested authentication type.
  4. Review the details — Thematic is a SaaS feedback analytics service and the MCP server's tools are read-only against the data already in your Thematic account. The full tool list and what each one does is documented above in this article.
  5. Select Approve, then grant tenant-wide consent for the required Microsoft Entra permissions when prompted.
  6. The server moves to the Registry tab with status Available. It can take up to 30 minutes for the server to propagate to all Copilot Studio environments in the tenant.

Once approved, makers consume the server the same way as Option 1 (Copilot Studio > Tools > Add a tool > Model Context Protocol > pick Thematic from the list of approved servers).

Prerequisites and notes

  • The maker needs a Copilot Studio license or an entitlement included with their Microsoft 365 Copilot plan.
  • Thematic's MCP servers use Streamable HTTP transport and OAuth 2.0 Dynamic Client Registration, both of which are supported and recommended by Copilot Studio. SSE transport, which Microsoft deprecated in August 2025, is not used.
  • For Option 2, all tool calls made by the agent are observable in Microsoft Defender Advanced Hunting — your security team can audit who invoked which Thematic tool, with what parameters, and what was returned.
  • Thematic data never leaves your selected region. Choose the regional server URL that matches where your Thematic account is hosted.