MCP Server Integration

The Lateo MCP server enables any MCP-compatible AI agent (Claude Code, Codex, etc.) to make private x402 payments.

Setup

Add to your MCP configuration (.claude/settings.json or claude_desktop_config.json):


{
  "mcpServers": {
    "lateo": {
      "command": "node",
      "args": ["/path/to/lateo/mcp-server/dist/index.js"],
      "env": {
        "STELLAR_SECRET_KEY": "S...",
        "LATEO_PROXY_URL": "http://localhost:3002",
        "AGENT_ID": "my-agent",
        "STELLAR_NETWORK": "stellar:testnet"
      }
    }
  }
}

Available Tools

`lateo_deposit`

Deposit USDC into the privacy pool.


lateo_deposit(amount: "5")

The operator signs transact() on behalf of the agent. A Groth16 proof is generated and verified on-chain.

`lateo_pay`

Pay for an x402 service through the pool.


lateo_pay(url: "http://localhost:3003/search?q=pharmaceutical+patents")

The payment is routed through the batch operator. On-chain, only “Pool → Service” is visible.

`lateo_balance`

Check your private balance in the pool.


lateo_balance()

Returns the current USDC balance available for payments or withdrawal.

Example: AI Agent Workflow


Agent: "Search for pharmaceutical patent filings in 2026"

1. Agent calls lateo_pay(url: ".../search?q=pharmaceutical+patent+filings+2026")
2. Proxy verifies agent has sufficient balance
3. Batch operator queues the x402 payment
4. Pool wallet executes the payment to zkSearch
5. zkSearch returns results
6. Agent receives the search results

On-chain: "Pool → zkSearch $0.001" — no agent identity visible.