Skip to main content
The Venice MCP Server is the official Model Context Protocol server for Venice. It exposes the full Venice API (chat, image, video, audio, music, embeddings, web augment, and characters) as 31 tools that any MCP-compatible agent can call.

GitHub: veniceai/venice-mcp-server

Published as @veniceai/mcp-server on npm. MIT licensed.

31 Tools

Every Venice modality in one config block

Any MCP Host

Claude Desktop, Cursor, ChatGPT, LM Studio, Continue, and more

Wallet Auth (Optional)

Bring an API key, or pay per call with a SIWE-signed wallet via x402

Quick start

1

Get a Venice API key

Generate one from venice.ai/settings/api. See the API key guide for step-by-step instructions.
2

Add Venice to your MCP host config

Drop this into your MCP host’s config file:
Common config paths:
3

Restart your MCP host

Your agent now has chat, image, video, music, TTS, ASR, and 25 more Venice tools available.
Most MCP hosts only pass environment variables that are explicitly listed in the env block. System-level env vars are not inherited. If you see 402 errors with an API key set, double-check that VENICE_API_KEY is inside env in your config.

What you get

31 tools spanning every Venice modality, 3 resources (venice://models, venice://styles, venice://voices), and 3 prompt templates.

Chat & embeddings

Image

Video

Audio (TTS / ASR)

Music

Web augment, catalog, and crypto

x402 wallet helpers

Only relevant if you authenticate with a wallet via x402 instead of an API key.

Configuration

The server is configured entirely through environment variables. If both VENICE_API_KEY and VENICE_SIWX_TOKEN are set, the API key wins.

x402 wallet mode

Venice supports authenticating with a Sign-In-With-X wallet token backed by prepaid USDC credit on Base or Solana, in addition to the normal API key flow. No email, phone, or KYC required: your wallet is the only identity.
The MCP server forwards VENICE_SIWX_TOKEN as the X-Sign-In-With-X header on every Venice API call. The server never sees your private key. Wallet signing and USDC top-up authorizations happen in your own wallet. Minimum top-up is $5 USD. Minimum balance to call inference is $0.10. Once topped up, calls are sub-100ms because settlement happens off-chain on a fast credit account.
Wallets linked to a Venice account with DIEM staked consume from the staking balance instead of USDC credits, so no top-up is needed.

Self-hosting (Streamable HTTP)

For team or workspace deployments, run the MCP server over HTTP instead of stdio:
The server is now available at http://localhost:3333/mcp. HTTP clients must send Authorization: Bearer <VENICE_MCP_AUTH_TOKEN>.
/mcp is a credential-backed tool execution endpoint: callers can spend the configured Venice API key or x402 balance. When HTTP mode binds outside loopback, startup fails unless VENICE_MCP_AUTH_TOKEN is set. For production, pin the npm package version explicitly instead of relying on latest.

Resources

GitHub

Source code, issues, and releases

npm

@veniceai/mcp-server

Venice Skills

Companion skills that teach agents how to use these tools

MCP Spec

Learn more about the Model Context Protocol