Agents · Claude Code

Claude Code + Hydrant.

Connect Claude Code to Hydrant's hosted MCP server so it can read issues, decisions, notes, cycles, milestones, and execution bundles from the terminal loop.

Install

Point the harness at Hydrant

Hydrant is a hosted MCP server. Use the harness-native configuration path and replace the example token with a personal access token from your workspace settings.

Endpoint: https://hydrant.dev/mcp
Config: ~/.claude.json for local or user scope; .mcp.json for project scope
Scope: Local is private to one project. Project scope is shareable through .mcp.json.

Claude Code install command

shell

claude mcp add --transport http hydrant https://hydrant.dev/mcp --header "Authorization: Bearer hyd_sk_your-token-here"

~/.claude.json for local or user scope; .mcp.json for project scope

json

{
  "mcpServers": {
    "hydrant": {
      "type": "http",
      "url": "https://hydrant.dev/mcp",
      "headers": {
        "Authorization": "Bearer hyd_sk_your-token-here"
      }
    }
  }
}

1
Create a Hydrant personal access token
Generate a token from Hydrant settings and keep it private. The token should belong to the workspace Claude Code needs to operate in.

Add the hosted MCP server

Use Claude Code's HTTP transport and pass the token as an Authorization header.

claude mcp add --transport http hydrant https://hydrant.dev/mcp \
  --header "Authorization: Bearer hyd_sk_your-token-here"

3
Choose the config scope deliberately
Use local scope for a private setup. Use project scope only when the team should share the server definition and each operator supplies their own token.

Verify

Check the connection

Reload the harness, confirm the MCP server is present, then ask the agent to call a small read-only Hydrant tool.

Reload

Restart Claude Code, or open /mcp in an active session and confirm hydrant is connected.

One-line tool call

Ask Claude Code: Use Hydrant to list_spaces.

Claude Code should call the Hydrant MCP server and return the workspaces your personal access token can see.

Skill catalog

Use your team's loop

These skills ship in .agents/skills/ and are harness-agnostic. Use them as a repeatable lifecycle, not as commands tied to one agent vendor.

shape

Shape the work

Plan the UX and UI before implementation starts.

refine

Clarify the brief

Turn rough requests into implementable Hydrant issues.

nail

Remove ambiguity

Tighten issue wording until the scope is unambiguous.

prep

Check readiness

Check readiness, dependencies, likely files, and branch state.

go

Do the work

Implement a ready issue end to end from Hydrant context.

preflight

Verify

Run the final quality gate before shipping.

yeet

Ship

Ship, merge, and clean up the branch once the work is ready.

Troubleshooting

Fix the common misses

Most connection failures are token, reload, or config-precedence issues. Check these before changing the Hydrant endpoint.

The server does not appear in /mcp

Run claude mcp list from the same project directory, then restart Claude Code. Local-scoped servers are stored under the current project entry in ~/.claude.json.

Authentication fails

Confirm the header is exactly Authorization: Bearer <token>, and verify the token has not been revoked from Hydrant settings.

Project .mcp.json prompts for approval

Claude Code asks operators to trust project-scoped MCP servers. Approve the Hydrant server once, or reset choices with claude mcp reset-project-choices if the wrong decision was saved.

Where to next

Finish the setup path

After the MCP server is connected, walk the quickstart once and keep the MCP surface reference nearby for tool names and common workflows.

Read quickstart MCP surface