TezosX MCP

A Model Context Protocol server for Tezos with x402 payment support.

Warning: This MCP is in beta. Most things should work, but please be prepared for troubleshooting. Please report any problems on our issues page.

As always, verify the output of your LLM before approving any transactions. Set reasonable limits. Trust but verify.

Components

MCP Server

Installation

The quickest path. Run the MCP locally alongside Claude Desktop — a built-in dashboard handles all configuration automatically.

1. Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

   {
     "mcpServers": {
       "tezos": {
         "command": "npx",
         "args": ["-y", "@ecadlabs/tezosx-mcp"]
       }
     }
   }

2. Restart Claude Desktop. Open your dashboard at localhost:13205, or ask Claude for the link.

3. Deploy your spending contract. Connect your wallet, deploy the spending contract, and set your spending limits. Everything else is handled for you.

Deploy on Railway or Render for a remote MCP that's still entirely under your control and accessible from multiple clients. Requires some manual configuration.

1. One-click deploy:

   

   

2. Open dashboard & deploy contract. Visit your deployment URL, connect your wallet, deploy the spending contract, and set your spending limits. Copy the provided spending key and contract address.

3. Set environment variables on your server:

   SPENDING_PRIVATE_KEY=edsk...
   SPENDING_CONTRACT=KT1...

4. Point Claude at your MCP:

   {
     "mcpServers": {
       "tezos": {
         "type": "streamable-http",
         "url": "https://your-mcp-url.example.com"
       }
     }
   }

Use our hosted dashboard to deploy your contract and generate keys, but run the MCP server locally. Keys never leave your browser.

1. Open the

2. Deploy contract & copy credentials. Connect your wallet, deploy the spending contract, and set your spending limits. Copy the provided spending key and contract address.

3. Add your copied variables to your Claude config:

   {
     "mcpServers": {
       "tezos": {
         "command": "npx",
         "args": ["-y", "@ecadlabs/tezosx-mcp"],
         "env": {
           "CONTRACT_ADDRESS": "KT1...",
           "SPENDING_PRIVATE_KEY": "edsk...",
         }
       }
     }
   }

1. Clone the TezosX-mcp repository

2. In the /TezosX-mcp/mcp folder run npm i && npm run build

{
  "mcpServers": {
    "tezosx": {
      "command": "node",
      "args": ["/path/to/TezosX-mcp/mcp/dist/index.js"]
    }
  }
}

Environment Variables

Available Tools

Web Dashboard

The MCP server includes a web dashboard for managing the spending wallet. It starts automatically on http://localhost:13205 (or your configured WEB_PORT).

Facilitator (Cloudflare Worker)

A Cloudflare Worker that verifies and settles x402 payments using the exact-tezos scheme.

Deploy

cd facilitator
npm install
npm run deploy

Configuration

Set TEZOS_RPC_URL in wrangler.jsonc:

{
  "vars": {
    "TEZOS_RPC_URL": "https://shadownet.tezos.ecadinfra.com"
  }
}

API

Notes:

• In-memory double-spend protection resets on deployment

• Only supports exact-tezos scheme with XTZ

• Operations must be verified before settlement

NFT Contract

Deploy the FA2 contract and authorize a minter:

cd mint
npm install
npm run deploy -- --minter tz1...

Mint Worker (Cloudflare Worker)

A Cloudflare Worker that mints Tezos NFTs when users pay via the x402 protocol. Returns 402 Payment Required until a valid payment is received, then mints an NFT receipt to the payer.

Features

• x402 payment protocol integration

• FA2-compliant NFT minting via Taquito

• Dynamic SVG receipt generation

• IPFS metadata storage via Pinata

Prerequisites

1. LIGO compiler - For compiling the NFT contract

2. Cloudflare account - For deploying the worker

3. Pinata account - For IPFS uploads (pinata.cloud)

4. Tezos wallet - Funded account for minting operations

Deploy

cd mint/worker
npm install
npm run deploy

Secrets

wrangler secret put TEZOS_RPC_URL      # e.g., https://shadownet.tezos.ecadinfra.com
wrangler secret put MINTER_PRIVATE_KEY # edsk...
wrangler secret put NFT_CONTRACT       # KT1...
wrangler secret put PAYMENT_RECIPIENT  # tz1...
wrangler secret put PINATA_JWT         # eyJ...

Configuration

Edit wrangler.jsonc:

{
  "vars": {
    "NETWORK": "shadownet",
    "PAYMENT_AMOUNT": "100000"  // 0.1 XTZ in mutez
  },
  "services": [
    { "binding": "FACILITATOR", "service": "tezos-x402-facilitator" }
  ]
}

The mint worker uses a service binding to call the facilitator directly (no public URL needed).

API

GET /mint - Mint an NFT after x402 payment

Query Parameters:

• recipient (optional) - Address to receive the NFT (defaults to payer)

Without payment (returns 402):

{
  "x402Version": 1,
  "paymentRequirements": [{
    "scheme": "exact-tezos",
    "network": "shadownet",
    "asset": "XTZ",
    "amount": "100000",
    "recipient": "tz1..."
  }]
}

With valid payment (returns 200):

{
  "success": true,
  "nft": {
    "tokenId": 42,
    "contract": "KT1...",
    "recipient": "tz1...",
    "metadataUri": "ipfs://Qm...",
    "opHash": "oo..."
  }
}

GET / - Health check

Error Codes

Architecture

┌──────────────────┐
│   Client/Agent   │
└────────┬─────────┘
         │ 1. GET /mint
         ▼
┌──────────────────┐
│  Mint Worker     │
└────────┬─────────┘
         │ 2. Return 402 with payment requirements
         ▼
┌──────────────────┐
│   Client/Agent   │
└────────┬─────────┘
         │ 3. Sign payment, retry with X-PAYMENT header
         ▼
┌──────────────────┐     ┌──────────────────┐
│  Mint Worker     │────▶│   Facilitator    │
└────────┬─────────┘     │   (verify)       │
         │               └──────────────────┘
         │ 4. Verified
    ┌────┴────┐
    ▼         ▼
┌────────┐ ┌────────┐
│ Pinata │ │ Tezos  │
│ (IPFS) │ │ (mint) │
└────────┘ └────────┘
         │
         │ 5. Return NFT details
         ▼
┌──────────────────┐     ┌──────────────────┐
│   Client/Agent   │     │   Facilitator    │
└──────────────────┘     │   (settle)       │
                         └──────────────────┘

License

Apache-2.0