MCP Server¶

The CLI includes qualytics mcp serve, a local bridge to the Model Context Protocol (MCP) server built into your Qualytics deployment. Use it when:

• The client only supports MCP servers that run as a local command (the stdio transport) and cannot connect to an HTTP endpoint.
• You already logged in with the CLI and want the assistant to reuse that session instead of managing a separate token.

Start the Server¶

qualytics mcp serve

The command reads the URL, token, and SSL setting saved by the CLI login (or the QUALYTICS_URL and QUALYTICS_TOKEN environment variables) and forwards every tool call to your deployment's MCP endpoint. MCP clients normally launch this command in the background; you rarely run it by hand.

Options¶

Register the Bridge in a Client¶

Register qualytics mcp serve as a command-based (stdio) MCP server. In Claude Code, for example:

claude mcp add qualytics -- qualytics mcp serve

Other clients follow the same pattern: the command is qualytics and the arguments are mcp serve. Check the client's documentation for where it stores command-based MCP servers.

HTTP Transport¶

To expose the bridge over the network, for example when the assistant runs on a different machine than the CLI:

qualytics mcp serve --transport streamable-http --host 0.0.0.0 --port 8000

Then point the client at http://<host>:8000. The bridge carries the full permissions of your CLI token, so restrict network access accordingly.

Available Tools¶

The bridge exposes the same tools as your deployment's MCP server, so the list is always current with your Qualytics version. See the MCP Deep Dive for what those tools can do. It adds one local tool, auth_status, which reports the CLI's configured URL, token validity, and expiry so the assistant can confirm the CLI is set up before making calls.