Connect Cursor and other MCP clients to Slaunt

Any Streamable HTTP MCP client with OAuth works. The difference from Claude Code and Codex is that there are no hooks, so Quaero only sees what the model reports. If the model never calls run_begin, the agent never appears. Install agent instructions in the client’s rules so it does.

.cursor/mcp.json

{
  "mcpServers": {
    "slaunt": { "url": "https://central-mcp-ccr-production.up.railway.app/mcp" }
  }
}

Use ~/.cursor/mcp.json for all projects. Other clients: point them at the same URL; OAuth is discovered from the 401 response. A minimal turn from the model:

thread_begin  { request_id: "<uuid>" }       # once per chat
run_begin     { task: "Fix flaky login test" }
ccr_search    { query: "login test flake" }
run_step      { activity: "Patched retry logic", progress: 60 }
ccr_log_event { type: "change", summary: "Fixed flaky login test by awaiting session cookie." }
run_end       { outcome: "completed" }

If one connection carries several chats, tag each request with a thread boundary, or they’ll all share one thread.

Get started

Clients

Protocol

Tools

Guides

Reference

Help

Connect Cursor and other MCP clients to Slaunt