Relay MCP

Quick install

Run the setup wizard to authenticate, install Relay MCP using local stdio, and auto-install native behavior bridges for supported clients. Relay uses instructions, rules, hooks, or skills only where the target tool has a real standards-based surface.

npx @onrelay/wizard

The default install path is local stdio. The wizard focuses on two surfaces only: the browser extension and MCP-connected coding agents.

Relay is designed to be used automatically and sparingly: start with get_brief, search only when local context is incomplete, and save only at meaningful boundaries.

Manual setup

If you prefer manual configuration:

1. Create an API token in Settings
2. Save your token to ~/.relay/mcp.json:

   {
     "apiBase": "https://onrelay.app",
     "token": "relay_your_token_here"
   }

3. Add the MCP server to your client config. Relay follows each client's native format instead of forcing one shared JSON schema:

   {
     "mcpServers": {
       "relay": {
         "command": "npx",
         "args": ["-y", "-p", "@onrelay/mcp", "relay-mcp"]
       }
     }
   }

Compatibility matrix

`validated` means Relay matches the current official format and has been checked recently. `supported` means Relay follows the published format but the integration surface is still narrower. `experimental` means the client is still installable, but Relay does not yet claim first-class polish.

Available tools

Relay's MCP surface is intentionally split between resume tools, writeback tools, and explainability tools. The explainability layer is what lets coding agents inspect why a brief or project state looks the way it does before mutating anything.