Harnesses

Connect your agent harness

Every supported harness speaks the Model Context Protocol. Add the Venym MCP server once and your agent gains live market data plus — with a key — perp trades, pair trades, and swaps.

Two transports work everywhere: local stdio (npx -y @venym/mcp, reads your key from VENYM_API_KEY) and remote HTTP (https://defi.venym.io/mcp, send your key in the Authorization header). Without a key, only public market-data tools are exposed.

New to MCP? Start with the MCP overview and the tool reference.

Claude Code

Config file: .mcp.json (project) or ~/.claude.json (user) · official docs ↗

local · stdio

{
  "mcpServers": {
    "venym": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@venym/mcp"],
      "env": { "VENYM_API_KEY": "venym_sk_live_..." }
    }
  }
}

remote · http

{
  "mcpServers": {
    "venym": {
      "type": "http",
      "url": "https://defi.venym.io/mcp",
      "headers": { "Authorization": "Bearer venym_sk_live_..." }
    }
  }
}

Or run: claude mcp add venym --env VENYM_API_KEY=venym_sk_live_... -- npx -y @venym/mcp. Verify with /mcp.

Codex CLI

Config file: ~/.codex/config.toml (or project .codex/config.toml) · official docs ↗

local · stdio

[mcp_servers.venym]
command = "npx"
args = ["-y", "@venym/mcp"]

[mcp_servers.venym.env]
VENYM_API_KEY = "venym_sk_live_..."

remote · http

[mcp_servers.venym]
url = "https://defi.venym.io/mcp"
bearer_token_env_var = "VENYM_API_KEY"

Or run: codex mcp add venym --env VENYM_API_KEY=venym_sk_live_... -- npx -y @venym/mcp. Verify with codex mcp list.

OpenCode

Config file: opencode.json (project) or ~/.config/opencode/opencode.json · official docs ↗

local · stdio

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "venym": {
      "type": "local",
      "command": ["npx", "-y", "@venym/mcp"],
      "enabled": true,
      "environment": { "VENYM_API_KEY": "venym_sk_live_..." }
    }
  }
}

remote · http

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "venym": {
      "type": "remote",
      "url": "https://defi.venym.io/mcp",
      "enabled": true,
      "headers": { "Authorization": "Bearer venym_sk_live_..." }
    }
  }
}

Hermes Agent

Config file: ~/.hermes/config.yaml · official docs ↗

local · stdio

mcp_servers:
  venym:
    command: "npx"
    args: ["-y", "@venym/mcp"]
    env:
      VENYM_API_KEY: "venym_sk_live_..."
    enabled: true
    supports_parallel_tool_calls: true   # market reads only

remote · http

mcp_servers:
  venym:
    url: "https://defi.venym.io/mcp"
    headers:
      Authorization: "Bearer venym_sk_live_..."
    enabled: true

Or run hermes mcp install and pick venym from the catalog.

OpenClaw

Config file: ~/.openclaw/openclaw.json · official docs ↗

local · stdio

{
  "mcp": {
    "servers": {
      "venym": {
        "command": "npx",
        "args": ["-y", "@venym/mcp"],
        "env": { "VENYM_API_KEY": "venym_sk_live_..." }
      }
    }
  }
}

remote · http

{
  "mcp": {
    "servers": {
      "venym": {
        "url": "https://defi.venym.io/mcp",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer venym_sk_live_..." }
      }
    }
  }
}

Tell your coding agent about Venym

Drop this into your project's AGENTS.md or CLAUDE.md so an agent working in your repo knows the contract:

markdown

## Venym DeFi (agent layer for DeFi)
- MCP server `venym` is configured (tools: get_orderbook, get_candles, execute_order,
  open_pair_position, swap_quote, ...). Prefer MCP tools over raw HTTP.
- For code, use @venym/sdk (TS) or the `venym` pip package (Python).
- API base: https://defi.venym.io/api. Public reads need no key; execution uses
  VENYM_API_KEY (scoped, risk-limited). Always pass an Idempotency-Key on retries.
- Docs: https://defi.venym.io/docs · llms.txt: https://defi.venym.io/llms.txt