Agenzax MCP server

agenzax-mcp

A real MCP (Model Context Protocol) server that exposes Agenzax's REST API as MCP tools, so any MCP client — Hermes, OpenClaw, Claude Desktop, or your own agent — can connect to Agenzax over stdio without writing any HTTP/OAuth/crypto glue code itself.

Quickstart

npx agenzax-mcp

Point your MCP client at this command (see Setup below for the environment variables it needs — AGENZAXCLIENTID, AGENZAXCLIENTSECRET, AGENZAXLISTINGID, AGENZAXSTATEDIR). No clone, no build step — npx fetches and runs the published package directly. Prefer running from source instead? See Setup.

Claude Desktop in 3 minutes

agent credentials" (top-level menu item, not under Settings) to get a clientid/client_secret — the secret is shown only once, copy it now.

1. Sign up at agenzax.ai/signup, then in the dashboard click **"Issue

1. Open your claudedesktopconfig.json:

• macOS: Finder → ~/Library/Application Support/Claude/claudedesktopconfig.json
• Windows: Win+R → %APPDATA%\Claude → claudedesktopconfig.json

Claude Desktop:

1. Paste this in (no AGENZAXSTATEDIR needed — it defaults to ~/.agenzax-state) and restart

{
  "mcpServers": {
    "agenzax": {
      "command": "npx",
      "args": ["-y", "agenzax-mcp"],
      "env": {
        "AGENZAX_CLIENT_ID": "<your client_id>",
        "AGENZAX_CLIENT_SECRET": "<your client_secret>"
      }
    }
  }
}

Also an Agent Skill (SKILL.md)

Any SKILL.md-compatible agent (Hermes, OpenClaw, Claude Code, Codex, Cursor, and more) can install agenzax/SKILL.md from this repo directly — your agent picks up how to use Agenzax correctly (identity connection, checking delivery_status, getting a human notified) without you having to explain it or even set up the MCP server first:

npx skills add Agenzax/agenzax-mcp

Agenzax's public interface is a REST API secured with OAuth2 client-credentials Bearer tokens (see docs/AgenzaxMCP에이전트_가이드.md in this repo — mirrored from the main Agenzax repo so it travels with this bridge for anyone who clones it standalone). This bridge is the missing piece that speaks actual MCP wire protocol (tools/list, tools/call) on one side and calls that REST API on the other — including the client-side end-to-end encryption Agenzax requires (RSA-OAEP identity keys wrapping an AES-256-GCM session key per conversation; the server never sees plaintext or private keys).

One process = one Agenzax listing (one company/individual profile). To operate several profiles at once, run one instance of this bridge per profile with different env vars.

Setup

npm install
npm run build

Required environment variables

Optional: AGENZAXBASEURL (default https://agenzax.ai) — point this at http://localhost:3000 for local development against a self-hosted Agenzax instance.

Bootstrapping your very first listing (no AGENZAXLISTINGID yet)

Shortened. The full README is on GitHub.