@0xgasless/mcp

@0xgasless/mcp

Give any AI agent a wallet. A Model Context Protocol server that exposes the whole 0xGasless platform — KMS-custodied agent wallets, x402 payments (zero gas), ERC-8004 identity / reputation / validation, and the Apify tool gateway — to any MCP host (Claude Code, Claude Desktop, Cursor, Windsurf…). One credential: your project API key.

27 tools across 7 domains: policy, agents, x402, identity, reputation, validation, tool-gateway. See SKILL.md for the full agent-facing integration guide.

Fastest path — one command

From a project directory:

OXGAS_API_KEY=0xgas_live_sk_... sh skills.sh

skills.sh writes the MCP config (.mcp.json, plus .cursor/mcp.json for Cursor projects), drops 0xgasless-SKILL.md as agent context, and prints next steps. Idempotent, no sudo, no global installs. Add --allow-spending to enable fund-moving tools.

Manual MCP config

{
  "mcpServers": {
    "0xgasless": {
      "command": "npx",
      "args": ["-y", "@0xgasless/mcp"],
      "env": {
        "OXGAS_API_KEY": "0xgas_live_sk_...",
        "OXGAS_DEFAULT_CHAIN": "fuji",
        "OXGAS_MCP_ALLOW_SPENDING": "0"
      }
    }
  }
}

Safety model

Read/create tools (create agent, read balance, get policy, search tools…) always work. Tools that move funds or write on-chain are marked [spending] and are refused by default:

• OXGAS_MCP_ALLOW_SPENDING=1 is required for any spending tool to run.
• Spending on a mainnet chain (avalanche, base) additionally requires I_UNDERSTAND_MAINNET=yes.

Refusals return a clear, actionable message instead of silently failing, and the only credential is the project API key — there is no private key to hold. This keeps an agent from spending without the operator explicitly opting in.

Local development

npm install
npm run build
OXGAS_API_KEY=... npm start      # runs the stdio server
npm run typecheck

Relationship to the old mcp/ package

The legacy 0xgasless-mcp (folder mcp/) wrapped agentkit with a raw private key and defaulted to BSC. This package is the platform model: KMS-custodied wallets via the project API key, x402, and the full ERC-8004 trust stack — no private key handling. Prefer this one.