Agents · Cursor

Cursor + Hydrant.

Connect Cursor's editor and cursor-agent CLI to Hydrant so Composer and terminal runs can use the same project context.

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
~/.cursor/mcp.json globally, or .cursor/mcp.json in a project
Scope
Project config is discovered from the workspace. Global config is available everywhere.
Cursor install command
shell
Open Cursor Settings -> MCP -> Add new MCP Server, or edit ~/.cursor/mcp.json.
~/.cursor/mcp.json globally, or .cursor/mcp.json in a project
json
{
  "mcpServers": {
    "hydrant": {
      "url": "https://hydrant.dev/mcp",
      "headers": {
        "Authorization": "Bearer hyd_sk_your-token-here"
      }
    }
  }
}
  1. 1

    Create a Hydrant personal access token

    Use a token scoped to the workspace you want Cursor and cursor-agent to operate in.

  2. 2

    Add mcp.json

    Use ~/.cursor/mcp.json for a machine-wide setup, or .cursor/mcp.json inside a project when only that workspace should load Hydrant.

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

    Reload Cursor

    Cursor's editor and CLI share MCP configuration. Reload the editor, then use cursor-agent mcp list if you want a terminal-side status check.

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

Reload Cursor, then check Settings -> MCP or run cursor-agent mcp list.

One-line tool call

Ask Cursor Agent: Use Hydrant to list_spaces.

Cursor should show hydrant as an MCP server and expose Hydrant tools to Composer, Chat, and cursor-agent.

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.

Cursor cannot find the server

Check whether you created global ~/.cursor/mcp.json or project .cursor/mcp.json, then reload the window from the project root.

cursor-agent disagrees with the editor

Run cursor-agent mcp list from inside the project. Cursor's CLI reports whether the config source is project or global.

The token works in one project but not another

Project mcp.json files can override global setup. Search parent directories for another .cursor/mcp.json before rotating the token.

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 quickstartMCP surface