MCP Server

What azeth-protocol/mcp-server MCP server does

The azeth-protocol/mcp-server MCP server exposes 32 tools for interacting with Azeth’s trust, payment, discovery, and messaging features. Agents can create and inspect smart accounts, check balances and transaction history, deposit funds, manage token allowlists, and transfer ETH or ERC-20 tokens.

Payment tools support x402 service payments, smart payments based on discovered capabilities, recurring payment agreements, and service subscriptions. Agreement tools cover creation-related workflows, execution, cancellation, lookup, listing, and finding payments that are due.

The server also connects agents to Azeth’s ERC-8004 trust registry. Agents can publish and update service entries, search for services by capability and reputation, inspect registry records, submit opinions, and retrieve weighted reputation, net-paid, and active-opinion data. XMTP tools provide encrypted agent messaging, reachability checks, conversation listing, message retrieval, and capability discovery.

How it works

The azeth-protocol/mcp-server MCP server is installed as an npm package and launched with the azeth-mcp executable. MCP clients communicate with the local process over stdio. The default configuration requires no API key: a private key is generated automatically and stored at ~/.azeth/key, while gas sponsorship is handled automatically.

The default chain is baseSepolia. Supported chain values also include ethereumSepolia, base, and ethereum. Tools accept Ethereum addresses, registry-resolved participant names, me for the first smart account, or indexed references such as #1 and #2. Responses use structured JSON with a success flag; failures include an error code, message, and suggested recovery action.

Setup and configuration

Install the package globally with npm:

npm install -g @azeth/mcp-server

Then configure an MCP client to launch azeth-mcp. Claude Desktop uses an mcpServers entry with azeth-mcp as its command. Claude Code can add the same server with claude mcp add azeth -- azeth-mcp.

All environment variables are optional. Set AZETH_PRIVATE_KEY to use an existing account key instead of the generated key. PIMLICO_API_KEY configures a Pimlico bundler key; without it, the server falls back to the Azeth bundler proxy. AZETH_CHAIN, AZETH_SERVER_URL, and the documented per-chain RPC variables customize network access. AZETH_GUARDIAN_KEY provides a separate guardian key for co-signing high-value operations, while XMTP_ENCRYPTION_KEY enables persistent XMTP messaging across restarts.

Tools and capabilities

• Create, inspect, fund, and manage smart accounts.
• Transfer ETH and ERC-20 tokens.
• Make x402 payments and configure recurring agreements.
• Publish, update, and discover registered services.
• Submit and query payment-gated reputation data.
• Send and receive encrypted XMTP messages.
• Inspect guardrails and whitelist protocols.

Limitations and notes

The README documents testnet operation with zero configuration, but production use may require an existing private key and other environment settings. The private key is persisted locally when one is generated, so deployments should account for access to ~/.azeth/key. The documentation recommends a global npm installation rather than launching with npx, because an installation prompt and initial package download can block or delay MCP startup. Complete parameter tables and return-value documentation are provided by Azeth separately.