Connect Claude

3 min read

Claude connects to Hawzu two different ways depending on which Claude you are using. Claude Code takes a pasted token; claude.ai and Claude Desktop use the sign-in flow.

Claude Code

Claude Code accepts an access token as a header, which is the simplest route.

Create an access token in Hawzu, setting Used for to MCP (AI clients). See Create an access token. There is no role or project to choose: an MCP token reads every project in the workspace you create it in, and nothing anywhere else. Give it a name and create it.

An existing API token will not work here — MCP and the REST API take separate tokens.

Add the server, pasting the token in place of YOUR_TOKEN:

claude mcp add --transport http hawzu https://app.hawzu.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Check it connected:
```
claude mcp list
```
Ask Claude something about your project. Start with “which Hawzu projects can you see?” — that exercises the connection end to end without needing to know any ids.

Claude Code can also use the sign-in flow. Add the server without a header and run /mcp to authenticate in the browser:

claude mcp add --transport http hawzu https://app.hawzu.com/mcp

Claude Desktop and claude.ai

These use custom connectors, which authenticate by signing in. There is no field to paste a token into.

Open Settings → Connectors and choose Add custom connector.
Enter the server URL:
```
https://app.hawzu.com/mcp
```
Confirm. Claude opens a Hawzu page asking you to approve the connection.
On the Hawzu consent screen, check the address the access will be sent to, choose which workspace the connection is for, then choose Allow read access.
You are returned to Claude with the connector enabled.

What to Ask

Claude does not know your project ids, so let it discover them:

“Which Hawzu projects can you see?”
“In the Checkout project, which test cases have never been executed?”
“Show me open critical defects raised in the last two weeks.”
“Is release 4.2 ready to ship?”

If It Does Not Connect

Symptom	Cause
`401` or “authentication failed”	The token is wrong, expired, or was revoked. Re-create it.
Connects, but every question is refused — token	The `workspace_id` being asked about is not the one the token was issued for, or the token has been revoked. An MCP token has no role to check; it reads one workspace.
Connects, but every question is refused — sign-in	Your own role cannot read that data. A connection acts as you, so it can never see more than you can.
”No projects”	The workspace has none, or — on a sign-in connection — you are not a member of any project in the workspace you approved.
Connector will not add	The URL must be exactly `https://app.hawzu.com/mcp`, with no trailing slash.
Claude describes a tool differently from these pages	It is working from the tool list it fetched when it connected. Start a new Claude Code session, or toggle the connector off and on. See Keeping a connection current.

Disconnecting

A pasted token is removed by removing the server from the client — and the token itself can be revoked from the Access Tokens page, which cuts off every client using it.

A sign-in connection is revoked under Settings → Security → Connected apps in Hawzu. It stops working on the client’s next call.