Thematic MCP Server

The Thematic MCP server lets AI assistants analyze your customer feedback data through natural conversation. Once connected, you can ask questions like "What are the top themes in our NPS survey?" or "Compare this quarter to last quarter" and the assistant will query Thematic on your behalf.

Server URL

This depends on the region your Thematic account is initialized in. This ensures that data remains in that region up till the point it is used by the calling LLM

Prerequisites

• A Thematic account (password or SSO login)
• Access to at least one organization with feedback data

Authentication

All clients use OAuth to authenticate. When you first connect, you'll be redirected to a login page where you enter your Thematic email, password (or SSO), and select your organization. After that, your session lasts for up to one year.

Available Tools

Once connected, the following tools are available to the AI assistant. You don't need to call these directly — just ask your questions naturally and the assistant will use the appropriate tools.

You shouldn't need to know the list below, the AI assistant has all this information and will make the choices on your behalf. It has a full description of all of the parameters

Management/Discovery Tools

Analysis/Reporting Tools

The below tools are for creating reports and extracting data from Thematic

Common Filter Parameters

The tools below accept any of these optional filter parameters in addition to a source identifier:

• text_search   (string) — Free-text search term.
• date_from   (string) — Start date YYYY-MM-DD   .
• date_to   (string) — End date YYYY-MM-DD   .
• segment_filters   (object) — Map of filter name to value(s), e.g. {"Region": "US"}   or {"Region": ["US", "EU"]}   .
• category   (array of issue   | request   | question   ) — Universally available feedback classification. Use for "how many issues / requests / questions" questions.
• sentiment   (array of positive   | neutral   | negative   ) — Universally available sentiment bucket.
• themes   (array of strings) — Filter to comments tagged with specific themes (titles like price   or codes like premium!price   ). Call get_themes   first to discover what's available.
• score_id   (string, where applicable) — Score to use (e.g. nps   , average   , sentiment   ). See get_source_info   . Defaults to the first available score.

Troubleshooting

Authentication fails or loops

• Clear your browser cookies for mcp.client.getthematic.com   and try again
• If you use SSO, make sure your identity provider session is active

Tools don't appear after connecting

• Start a new conversation — tools are loaded at conversation start
• Check that the server shows as "Connected" in your client's MCP settings

"Organization not found" errors

• Use the Switch Organization tool to verify your available organizations
• Ask the assistant: "List my available organizations"

Session expired

• Sessions last up to one year. If yours expires, disconnect and reconnect the server to re-authenticate.

Connecting your tools

This section details instructions on how to connect to the Thematic MCP server from your tool of choice.

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.

Option 1: Connect via a Copilot Studio agent (recommended)

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.

Gemini CLI

Gemni CLI supports connecting MCP servers through commands in the CLI. To connect Thematic you will have to first add it to your settings file, and then authenticate it.

Step 1: Add to .gemini/settings.json

This file should be in the folder you are running Gemini CLI from.

If this file does not exist you may have to make it. The minimal file is below, but if you already have one with mcpServers defined you will have to add just the "thematic":{"httpUrl":} section.

Remember to replace the url with the correct one for the region you want to connect to.

{
  "mcpServers": {
    "thematic": {
      "httpUrl": "https://mcp.client.getthematic.com"
    }
  }
}

Step 2: Authenticate the MCP server

Once this has been done, restart your Gemini CLI. You can then run (inside Gemini CLI):

/mcp auth thematic

This will guide you through the process of authenticating the MCP server in the browser, and then come back to Gemini CLI.

Gemini Enterprise

Gemini Enterprise supports remote MCP servers via the Custom MCP Server data store (currently in preview).

Unlike Claude.ai or ChatGPT, this is an admin-only setup — end users cannot connect MCP servers themselves. These steps apply to Gemini Enterprise Standard, Plus, and Frontline editions. MCP is not available in the Business edition, nor in Gemini features bundled into Google Workspace.

Preview limitation: VPC Service Controls are not supported while Custom MCP Server data stores are in preview.

Step 1: Override the organization policy

By default, Google Cloud blocks creation of Custom MCP Server data stores. An admin with the Organization Policy Administrator role (roles/orgpolicy.policyAdmin   ) must override this:

1. In the Google Cloud console, go to IAM & Admin > Organization Policies
2. Select your project
3. Filter for Disable custom mcp server connector for gemini enterprise  
4. Click the policy, then Manage Policy
5. Select Override parent's policy, add a rule, set enforcement to Off, and click Set Policy

Step 2: Create a client in Thematic MCP

Navigate to the Thematic MCP Client management page here and login using your Thematic credentials.

Create a new client, for the Redirect URI you must use:

https://vertexaisearch.cloud.google.com/oauth-redirect

Make sure to copy the Client ID and Client Secret on the next page. The secret will not be able to be retrieved later.

Step 3: Create the data store

Requires the Discovery Engine Editor role (roles/discoveryengine.editor   ).

1. In the Google Cloud console, go to Gemini Enterprise > Data stores > Create data store
2. Search for Custom MCP Server   and click the Custom MCP Server (Preview) card, then Add MCP server
3. In Authentication settings
   1. MCP Server URL  Enter the Thematic MCP server URL from the table at the top of this article (for example, https://mcp.client.getthematic.com for US)
   2. Authorization URL  Enter the Thematic MCP server URL from the table at the top, followed by /oauth/authorize (for example https://mcp.client.getthematic.com/oauth/authorize  for the US)
   3. Token URL Enter the Thematic MCP server URL from the table at the top, followed by /oauth/token (for example https://mcp.client.getthematic.com/oauth/token  for the US)
   4. Enter the client id and secret you created in step 2
   5. Enter the following for scopes: openid name email picture offline_access read:organization read:result read:survey read:visualization read:user read:themes view:analysis read:lens manage:user

   6. 

4. Click Login and authenticate with your Thematic credentials.
5. Click Continue, then add an MCP Server Description to help Gemini route relevant queries to Thematic. For example: "Customer feedback analytics from Thematic. Use for questions about feedback themes, sentiment, theme trends, period-over-period comparisons, and individual comments."
6. Set the Location, give the data store a Name (e.g. Thematic), and click Create
7. Wait for the data store status to change to Active

Step 3: Enable Thematic tools

By default no tools are enabled.

1. Open the Thematic data store
2. Go to the Actions tab and click Reload custom actions to reauthenticate
3. Toggle on the tools you want available to users

Step 4: Connect the data store to your Gemini Enterprise app

1. From Gemini Enterprise > Apps, select your app
2. Click Connected data sources > Add existing data stores
3. Select your Thematic data store and click Connect

Once connected, users can authorize Thematic from the Connections panel in Gemini Enterprise and start asking questions. Each user authenticates with their own Thematic credentials.