MCP setup

Connect Cursor to Strazh

connects directly over HTTP — no bridge needed

The endpoint URL and auth token are specific to your own local Strazh install — they live in Settings → Connect inside the app, not on this page. Copy them from there when a step below asks for them.

1Get your endpoint and token

Open Strazh, go to Settings → Connect, and copy the endpoint URL and auth token shown there. Both are specific to your own local install.

2Add a server entry

Cursor can connect directly to an HTTP MCP endpoint. Add a server entry pointing at the endpoint and token above — the exact settings-file location and key names vary by Cursor version, so check Cursor’s own MCP docs for exactly where to add this. The general shape every HTTP-based MCP client config takes:

{
  "mcpServers": {
    "strazh": {
      "url": "<endpoint URL from Strazh Settings → Connect>",
      "headers": {
        "X-Strazh-Token": "<auth token from Strazh Settings → Connect>"
      }
    }
  }
}

Available tools

Every tool call funnels through the exact same gate every other Strazh entry point uses — capped, allow-listed, and audited identically:

  • dispatch — Dispatch a coding agent (claude_code, codex, cursor, or devin) against an allow-listed repository, through Strazh's safety gate.
  • list_allowed_roots — List the directories currently on Strazh's dispatch allow-list.
  • add_allowed_root — Add a directory to Strazh's dispatch allow-list.
  • remove_allowed_root — Remove a directory from Strazh's dispatch allow-list.
  • list_agents — List the coding agents Strazh knows about and whether each is available.
  • get_usage — Current license tier and today's dispatch usage against the tier cap.
← Back to install & setup
Connect Cursor to Strazh's MCP server