Venum MCP

Composable Solana execution infrastructure, for coding agents.

@venumdev/mcp is the MCP server for the Venum Solana execution stack. It gives coding agents and trading agents a stable tool surface for prices, pools, quotes, swap building, local signing + submission, and transaction tracking. It is designed to work with Venum Skills for higher-level workflows and agent context.

• Website: www.venum.dev
• CLI: github.com/venumhq/solana-venum-cli
• Skills: github.com/venumhq/solana-venum-skills
• Terminal: github.com/venumhq/solana-venum-terminal

Venum's core product direction stays the same:

Less raw RPC. More executable actions.

This repo is the MCP-native part of that OSS surface.

What It Does

• Exposes Venum execution primitives as MCP tools
• Wraps the Venum CLI in JSON mode for stable machine-readable tool results
• Keeps the initial tool surface narrow and composable
• Fits coding-agent and trading-agent workflows better than raw RPC glue

Tool Surface

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

Install

@venumdev/mcp shells out to @venumdev/cli internally. If you run it with pnpm dlx @venumdev/mcp, the CLI dependency is handled automatically. If you run from a checked-out repo, install dependencies first with pnpm install.

Run without installing:

pnpm dlx @venumdev/mcp

Install globally:

pnpm add -g @venumdev/mcp
venum-mcp

Install locally:

pnpm add @venumdev/mcp

API Key

Most Venum tools require an API key.

Get one at www.venum.dev, then configure the underlying CLI once:

venum config set api-key <your-key>

If you already saved your key with venum config set api-key, @venumdev/mcp will reuse that config automatically through the Venum CLI. In that case, you usually do not need to pass VENUM_API_KEY again in the MCP client config.

Or pass environment variables to the MCP process:

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

How It Works

The current implementation is intentionally thin:

• MCP receives a tool call
• the server invokes @venumdev/cli
• the CLI runs in --json mode
• the MCP server returns the parsed JSON result to the agent

This keeps the tool contract stable while the broader Venum SDK and MCP surface evolves.

Example MCP Config

If your machine already has a saved Venum CLI config, this is enough:

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

If you want to pass the API key directly to the MCP process:

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

This works well for Claude, OpenCode, and other stdio-based MCP clients.

You can also use a global install instead of pnpm dlx:

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

Development

pnpm install
pnpm start
pnpm check
pnpm publint

Why This Exists

The Venum plan is to build the composable Solana execution layer for coding agents and trading agents.

That means:

• CLI-first workflows
• JSON-native outputs
• stable tool semantics
• fewer moving parts than raw RPC plus custom infra glue

@venumdev/mcp is the direct expression of that strategy.

License

MIT