Skip to main content
The ClarityQ MCP server lets you ask ClarityQ questions from an AI assistant such as Claude, Claude Code, or Cursor. The assistant sends your question to ClarityQ, and ClarityQ answers it the same way it does in Ask Anything — using your Context Layer, your data warehouse, and your permissions.
This is the opposite direction from MCP Connectors. MCP Connectors bring outside tools into ClarityQ. The ClarityQ MCP server brings ClarityQ into your AI assistant.

​
Prerequisites

  • MCP access turned on for your organization. It’s off by default; ask your ClarityQ account manager to turn it on.
  • A ClarityQ account with a role that can use Ask Anything in at least one product. Viewers can’t ask questions through the MCP server.
  • An AI assistant that supports remote MCP servers with sign-in (OAuth). This includes Claude (web and desktop), Claude Code, and Cursor.

​
Server URL

Use this URL in every client:

​
Claude (web and desktop)

1

Add a custom connector

In Claude, go to Customize → Connectors and click Add custom connector. On Claude Team and Enterprise plans, an organization owner adds the connector once under Organization settings → Connectors, and members then click Connect.
2

Enter the server URL

Name the connector ClarityQ and paste https://agent.clarityq.ai/mcp as the URL. Leave the OAuth client fields empty.
3

Sign in to ClarityQ

Claude opens the ClarityQ sign-in page. Sign in with the same method you use for the ClarityQ app — email and password, Google, or your company’s single sign-on.
4

Approve access

Review the consent screen and click Accept. Claude can now ask ClarityQ questions on your behalf.

​
Claude Code

Add the server from your terminal:
Then run /mcp inside Claude Code, select clarityq, and choose Authenticate. A browser tab opens the ClarityQ sign-in page; sign in and approve access.

​
Cursor and other MCP clients

Add a remote (HTTP) MCP server with the URL https://agent.clarityq.ai/mcp in your client’s MCP settings. The client opens the ClarityQ sign-in page the first time it connects.

​
Staying Signed In

You sign in once per client. Your assistant renews access automatically in the background, so you don’t need to sign in again each session. You’ll be asked to sign in again only if your access is revoked or you remove and re-add the connector.
If you’re already signed in to ClarityQ in the same browser, the sign-in step may be skipped and you’ll go straight to the consent screen.

​
Disconnecting

Remove the connector from your assistant’s connector or MCP settings — for example Customize → Connectors in Claude, or claude mcp remove clarityq in Claude Code. Your ClarityQ conversations and data are not affected.