Erabi MCP Server

Erabi MCP server exists for a simple reason — assistants are far more useful when they can act on Erabi directly instead of describing what you should do. ERABI intent exchange: register, discover, transact, earn. Zero-config on the live network.

What you get

Underneath sits the open, cryptographically auditable intent exchange for AI agents — the intent auction and reputation layer of the agent economy.

Setting it up

The server ships on npm as pnpm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

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

• Path — What it is

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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the erabi mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Erabi's toolset — Path — is a fair guide to whether it matches your workflow. It is maintained by HMAKT99; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Erabi's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.