Venum

Appearance

Solana Venum MCP ​

Use @venumdev/mcp when you want coding agents or trading agents to call Venum through a stable MCP tool surface instead of wiring raw Solana RPC and HTTP flows by hand.

The MCP server exposes Venum execution primitives for:

  • health checks
  • price lookups
  • pool discovery
  • token discovery
  • swap quotes
  • swap builds
  • local signing and submission
  • transaction status

Install ​

Run without installing:

bash
pnpm dlx @venumdev/mcp

Install globally:

bash
pnpm add -g @venumdev/mcp
venum-mcp

Install locally:

bash
pnpm add @venumdev/mcp

API Key ​

Most MCP tools require a Venum API key.

If you already configured the CLI, the MCP server reuses it automatically:

bash
venum config set api-key <your-key>

You can also pass environment variables directly to the MCP process:

bash
VENUM_API_KEY=<your-key>
VENUM_API_URL=https://api.venum.dev

How It Works ​

The current server is intentionally thin:

  1. The MCP client sends a tool call.
  2. @venumdev/mcp invokes @venumdev/cli in --json mode.
  3. The server returns the parsed result back to the agent.

That keeps the tool contract stable while the broader Venum SDK and agent surface evolves.

Tool Surface ​

Current MCP tools:

  • health
  • price
  • prices
  • pools
  • tokens
  • quote
  • swap_build
  • swap_sign_and_submit
  • tx_status

Example MCP Config ​

If your machine already has a saved Venum CLI config:

json
{
  "mcpServers": {
    "venum": {
      "command": "pnpm",
      "args": ["dlx", "@venumdev/mcp"]
    }
  }
}

If you want to pass the API key directly:

json
{
  "mcpServers": {
    "venum": {
      "command": "pnpm",
      "args": ["dlx", "@venumdev/mcp"],
      "env": {
        "VENUM_API_KEY": "<your-key>"
      }
    }
  }
}

With a global install:

json
{
  "mcpServers": {
    "venum": {
      "command": "venum-mcp"
    }
  }
}