rwa.wtfdocs
MCP

Connect

Create an API key and connect an MCP client to rwa.wtf.

rwa.wtf uses an HTTP MCP endpoint. Choose the lowest permission level that fits the task.

ScopeMarket dataAccount dataPlace and manage orders
IntelYesNoNo
TradeYesYesYes, with real funds

Trade is the higher-permission scope. A Trade key includes every Intel route, plus 6 account and order tools.

Connect · View Intel routes · View Trade routes

Create a key

  1. Sign in to the terminal and open the account panel.
  2. Under Agent API keys, select Read only for Intel routes or Trade for the higher-permission scope.
  3. Enter a name, then select Create key.
  4. Copy the key. It is shown once.

Keys are stored as hashes. A lost key cannot be recovered. Create a replacement and revoke the old key.

Use an Intel key unless the agent needs to read the account or submit orders. Trade keys can place orders without another browser confirmation.

Configure the client

Add the HTTP MCP endpoint and key to the client's MCP configuration:

{
  "mcpServers": {
    "rwa-wtf": {
      "type": "http",
      "url": "https://api.rwa.wtf/v1/mcp",
      "headers": {
        "Authorization": "Bearer rwa_live_YOUR_KEY"
      }
    }
  }
}

Restart the MCP client after changing its configuration.

Verify the connection

Run tools/list in the MCP client:

ScopeExpected tools
Intel31
Trade37

An Intel key should not list account or order tools. A Trade key should list the same 31 Intel tools and 6 additional account and order tools.

Key handling

  • Do not place keys in prompts, source code, screenshots, or public configuration files.
  • Revoke a key from the account panel when it is no longer needed.
  • Revoking a Trade key does not cancel resting orders or close positions.
  • No API key can deposit, withdraw, add a withdrawal address, or start a venue migration.

All keys owned by 1 account share the limits documented on the Intel page. Creating another key does not add capacity.

On this page