MCP Overview
3 min read
Hawzu ships an MCP server. It lets an AI client — Claude, ChatGPT, Cursor, or anything else that speaks the Model Context Protocol — read your project’s records so you can ask questions of your test data in the tool you already work in.
It is read only. The server exposes no way to create, edit or delete anything, in any project, for any credential.
What a Connected Client Can Read
Section titled “What a Connected Client Can Read”Test cases, requirements and tasks, defects, releases, test runs and run results, labels, shared steps, parameters, and custom field definitions.
It can also run structured queries across those records — “test cases in this release that failed and have an open defect” is a single question, not four — and fetch a release’s readiness scorecard.
What It Cannot Do
Section titled “What It Cannot Do”If your role cannot open the Defects screen, a connected client is refused when it asks about defects. It is told it was refused, rather than shown an empty list — so an AI cannot report “no open defects” when the truth is “you may not look”.
Two Ways to Connect
Section titled “Two Ways to Connect”Which one you use depends on the client, not on preference. Some clients only support one.
| Method | Acts as | Use with |
|---|---|---|
| MCP access token | The robot account the token belongs to | Claude Code, Cursor, VS Code, the OpenAI API |
| Sign in with Hawzu | You | Claude, Claude Desktop, ChatGPT |
An MCP access token is pasted into the client’s configuration as a header. It is issued by a workspace administrator, reads every project in that workspace and nothing anywhere else, and does not expire unless it was given an expiry. There is no scope to choose: give it a name and create it.
Sign in with Hawzu opens a browser, asks you to approve the connection for one workspace, and gives the client a credential that acts as you in that workspace. It expires hourly and refreshes silently. You can revoke it yourself at any time, and so can an administrator of that workspace.
The Server Address
Section titled “The Server Address”It speaks Streamable HTTP, and supports every protocol revision from 2025-03-26 through the current 2026-07-28 — so a client does not have to be recent to connect. There is no local install, no npm package and no gateway to run, and no session: each call stands alone.
Keeping a Connection Current
Section titled “Keeping a Connection Current”Hawzu improves the MCP server over time — new tools, and better instructions to the ones that exist. Two different things happen to an existing connection when it does.
Your answers are always current. Everything a tool returns — your records, the vocabulary of a project, the guidance a client reads before writing a query — comes fresh from Hawzu on every call. Nothing is cached, so a connection made months ago answers with today’s data and today’s rules.
The list of tools is fetched once per session. A client asks what tools exist when it connects, then works from that answer. So a new tool, or a reworded description of an existing one, arrives when the client next connects — not while it is running.
There is no notification when this happens, deliberately: the server keeps no connection open to any client, which is what lets it run without sessions. So it is worth a reconnect if a client seems to be describing a tool differently from these pages.