Azeth MCP Server

MCP server for Azeth — smart accounts, payments, reputation, and discovery tools for AI agents

Local serverstdio

What is the Azeth MCP server?

Azeth MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for Azeth — smart accounts, payments, reputation, and discovery tools for AI agents.

What you get

MCP (Model Context Protocol) server for Azeth -- the trust, discovery, and payment layer for the machine economy. Provides 32 tools for AI agents to create accounts, make payments, discover services, manage reputation, and communicate via XMTP.

What the assistant can call

Once Azeth is connected, these are the calls the assistant has available:

  • Category — Tools
  • Messaging — The Messaging tool exposed by this server

Configuration and credentials

You will need 5 environment variables: AZETH_PRIVATE_KEY, PIMLICO_API_KEY, AZETH_SERVER_URL, AZETH_GUARDIAN_KEY, XMTP_ENCRYPTION_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@azeth/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Azeth's toolset — Category, Messaging — is a fair guide to whether it matches your workflow. It is maintained by azeth-protocol; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the azeth mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTools
MessagingThe Messaging tool exposed by this server.

How to install the Azeth MCP server

{
  "mcpServers": {
    "azeth": {
      "command": "azeth-mcp"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AZETH_PRIVATE_KEYCredential the server authenticates with.Yes
PIMLICO_API_KEYCredential the server authenticates with.Yes
AZETH_SERVER_URLEndpoint or connection string the server talks to.Yes
AZETH_GUARDIAN_KEYCredential the server authenticates with.Yes
XMTP_ENCRYPTION_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Azeth to Category.
  • Use Azeth to Messaging.

Frequently asked questions

No API keys required. A private key is auto-generated and saved to `~/.azeth/key`. For production, you can set the `AZETH_PRIVATE_KEY` environment variable to use an existing key.