Rath MCP

Use Rath MCP when you want an AI coding assistant or agent to work with xPath routing or Tachyon relay APIs through structured Model Context Protocol tools.

The public MCP endpoint exposes Rath's xPath and Tachyon tools:

https://mcp.rath.fi/mcp

xPath and Tachyon use the same MCP endpoint. Add your product API keys as MCP request headers to enable authenticated tools.

CLI commands

claude mcp add --transport http rath https://mcp.rath.fi/mcp

codex mcp add rath --url https://mcp.rath.fi/mcp

Quick setup

Add the server to any MCP-compatible client. Configure only the keys for the products you intend to use:

{
  "mcpServers": {
    "rath": {
      "url": "https://mcp.rath.fi/mcp",
      "headers": {
        "xpath-api-key": "YOUR_XPATH_API_KEY",
        "tachyon-api-key": "YOUR_TACHYON_API_KEY"
      }
    }
  }
}

Treat MCP headers as secrets. Use environment-variable substitution when your MCP client supports it, and never commit API keys to a repository.

Installation with your IDE

Select your MCP client to view setup instructions.

Open a project in Cursor and navigate to Cursor Settings.
In the settings menu, go to the MCP section.
Click New MCP Server. This opens your mcp.json configuration file.
Add the following configuration:

{
  "mcpServers": {
    "rath": {
      "url": "https://mcp.rath.fi/mcp",
      "headers": {
        "xpath-api-key": "YOUR_XPATH_API_KEY",
        "tachyon-api-key": "YOUR_TACHYON_API_KEY"
      }
    }
  }
}

Return to the MCP settings page and enable the server using the toggle switch next to rath.

For more information, see the Cursor MCP documentation.

Add Rath MCP from your terminal:

claude mcp add --transport http rath https://mcp.rath.fi/mcp

Verify that Claude Code can see it:

claude mcp get rath

Add xpath-api-key and tachyon-api-key as custom HTTP headers in the generated Rath MCP configuration before calling authenticated tools.

Start Claude Code and ask it to quote xPath routes, inspect supported chains, build transaction payloads, or generate a Tachyon SDK integration.

For more information, see the Claude Code MCP documentation.

Open your Windsurf MCP configuration file:

~/.codeium/windsurf/mcp_config.json

Add the Rath server:

{
  "mcpServers": {
    "rath": {
      "url": "https://mcp.rath.fi/mcp",
      "headers": {
        "xpath-api-key": "YOUR_XPATH_API_KEY",
        "tachyon-api-key": "YOUR_TACHYON_API_KEY"
      }
    }
  }
}

Save the file and enable the rath server in Windsurf's MCP settings.

For more information, see the Windsurf MCP documentation.

Open Kiro and go to Preferences or Settings.
Search for MCP and enable MCP support.
Create or open the MCP configuration file:

./.kiro/settings/mcp.json

Add the Rath server:

{
  "mcpServers": {
    "rath": {
      "url": "https://mcp.rath.fi/mcp",
      "headers": {
        "xpath-api-key": "YOUR_XPATH_API_KEY",
        "tachyon-api-key": "YOUR_TACHYON_API_KEY"
      },
      "disabled": false
    }
  }
}

Save the file and reload Kiro so the rath MCP server appears in the MCP tab.

For more information, see the Kiro MCP documentation.

Available xPath tools

Rath MCP exposes xPath tools for token discovery, route quoting, transaction construction, calldata generation, gasless swaps, and status tracking:

Tool	Purpose
`xpath_list_tokens`	List tokens supported by xPath, optionally filtered by chain ID
`xpath_search_token`	Search for a token by symbol, name, or address
`xpath_get_supported_chains`	Get chains supported by xPath
`xpath_get_quote`	Get a same-chain or cross-chain route quote
`xpath_build_path`	Build an unsigned transaction payload from an explicit route request
`xpath_build_transaction`	Build an unsigned transaction payload from a quote ID
`xpath_build_best_path`	Find the best route and build its unsigned transaction payload
`xpath_get_transaction_status`	Get transaction status by transaction hash and source chain
`xpath_build_calldata`	Build raw xPath calldata for advanced integrations
`xpath_get_gasless_quote`	Get a gasless quote with Permit2 EIP-712 signing data
`xpath_submit_gasless_swap`	Submit a signed gasless swap
`xpath_get_gasless_status`	Get gasless swap status by swap ID or transaction ID

Tachyon tools help coding agents implement Tachyon correctly without using a shared server-side Tachyon account. Authenticated calls use the API key from the current request's tachyon-api-key header. Status and account lookup use Tachyon's read-only public endpoints:

Tool	Purpose
`tachyon_get_supported_chains`	List chains supported by Tachyon using the public discovery endpoint
`tachyon_generate_integration_code`	Generate TypeScript SDK or REST examples for relay, sync relay, quote, status, or supported chains
`tachyon_get_api_reference`	Return endpoint, authentication, request, response, and status details
`tachyon_validate_transaction`	Validate relay parameters and Tachyon-specific constraints locally
`tachyon_quote_transaction`	Estimate relay cost and minimum required balance
`tachyon_submit_transaction`	Submit an asynchronous relay transaction after explicit confirmation
`tachyon_submit_transaction_sync`	Submit and wait for a hash, terminal status, or timeout after explicit confirmation
`tachyon_get_transaction_status`	Retrieve relay status, execution hash, receipt, or revert information
`tachyon_get_account_information`	Retrieve Tachyon account balance, configuration, and pending costs

tachyon_submit_transaction and tachyon_submit_transaction_sync require confirm: true. An agent should set it only after the user approves the chain, destination, value, calldata, estimated cost, and account charge.

Rath MCP does not accept private keys and does not sign wallet transactions. API keys are forwarded only to their matching Rath API for the current tool call and are not returned in tool responses.

Rath MCP

CLI commands

Quick setup

Installation with your IDE

Available xPath tools

Available Tachyon tools

On this page