Connecting an MCP Client
Point Claude, Cursor, or any MCP client at the Query Security Data Mesh
TL;DRPoint your client at
https://mcp.query.ai/mcpover streamable HTTP.Clients that support OAuth register themselves and prompt you to sign in. Others authenticate with a Query API token in the
x-token-authorizationheader.Enable only the tools you need — schemas are re-sent each reasoning turn.
Authentication
OAuth (preferred)
Clients supporting the MCP authorization spec need no credential in their configuration. On first connection the client discovers the authorization server, registers itself dynamically, and opens a browser for you to sign in and approve access. The client stores and refreshes the resulting tokens.
{
"mcpServers": {
"query": {
"url": "https://mcp.query.ai/mcp"
}
}
}Claude Code:
claude mcp add --transport http query https://mcp.query.ai/mcpRun /mcp in Claude Code to start the sign-in, and to check or re-authenticate a connection later.
API Token
For clients that do not support OAuth, send a Query API token in a header:
{
"mcpServers": {
"query": {
"url": "https://mcp.query.ai/mcp",
"headers": {
"x-token-authorization": "YOUR_QUERY_API_TOKEN"
}
}
}
}claude mcp add --transport http query https://mcp.query.ai/mcp \
--header "x-token-authorization: YOUR_QUERY_API_TOKEN"Claude Desktop and Cursor
Add the relevant block above to the client's MCP configuration and restart.
Charlotte AI
AgentWorks has its own registration flow — see Connecting Charlotte AI to the Query Mesh.
Verify
Ask the assistant which connectors are available on your mesh. A list confirms the token, endpoint, and tool wiring together.
To check the query path specifically, ask it to run EXPLAIN VERSION, which returns the FSQL and data model versions without touching a connector.
Choosing Tools
For investigation work, these five are usually sufficient:
- Execute FSQL Query
- Validate FSQL Query
- Search FSQL Schema
- FSQL Query Generation
- FSQL Connectors
Add translation, Worker, or organization tools when a workflow needs them. Each attached tool's schema is typically re-sent on every reasoning turn, so unused tools cost tokens on every exchange rather than only when called.
Update Environment Profile modifies your Query organization's configuration. Leave it disabled unless you intend an assistant to change it.
What's Next
Updated about 1 hour ago