MCP Server

How it works

The MCP server runs as a local stdio process. It never binds a network port, and your credentials are sent only to the RaceHooks API to obtain an access token. It exposes 59 tools, 7 live resources, and 6 guided prompts to any MCP-compatible client. Every call uses your account's credentials, so what a tool returns depends on your plan. Token refresh is handled automatically.

Installation

npm install -g @racehooks/mcp

Or run directly without installing:

npx -y @racehooks/mcp

The server needs RACEHOOKS_CLIENT_ID and RACEHOOKS_CLIENT_SECRET in its environment and exits on start-up without them.RACEHOOKS_BASE_URL is optional and defaults to https://api.racehooks.io.

Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the Windows equivalent:

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID":     "your-client-id",
        "RACEHOOKS_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Claude Code

Add the server with the Claude Code CLI:

claude mcp add racehooks \
  -e RACEHOOKS_CLIENT_ID=your-client-id \
  -e RACEHOOKS_CLIENT_SECRET=your-client-secret \
  -- npx -y @racehooks/mcp

Add --scope project to share it with your team through a project .mcp.json, or --scope user to use it in every project. To commit .mcp.json without secrets, reference environment variables:

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID":     "${RACEHOOKS_CLIENT_ID}",
        "RACEHOOKS_CLIENT_SECRET": "${RACEHOOKS_CLIENT_SECRET}"
      }
    }
  }
}

Cursor / Windsurf

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID":     "your-client-id",
        "RACEHOOKS_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Windsurf uses the same JSON in ~/.codeium/windsurf/mcp_config.json.

Example prompts

Tools

All tool inputs are validated with Zod schemas that Claude uses to generate high-quality arguments. The plan line is what the API enforces for that tool.

Resources

Resources are read-only named contexts the assistant loads into its context window without you having to ask. They stay fresh because they are fetched live on each request.

Guided prompts

Prompts are workflows that work like slash commands in supporting clients (Claude Desktop, Claude Code). They accept parameters and generate a complete conversational setup sequence.

Security