Ethora MCP Cli MCP Server

MCP server for the Ethora chat & messaging platform: login, manage apps and chat rooms, broadcast messages, and deploy AI agents / chatbots with RAG sources. The ethora mcp cli mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.

What it actually does

An MCP (Model Context Protocol) CLI/server that connects popular MCP clients to the Ethora platform — an open-source chat & messaging platform with a built-in AI agent / chatbot framework. This runs locally on a developer machine via stdio rather than as a hosted Ethora service. Use it from Cursor, VS Code MCP, Claude Desktop, or Windsurf/Cline to manage apps and chat rooms, broadcast messages, deploy AI agents / chatbots with RAG sources, and automate B2B provisioning workflows. (ERC-20 wallet tools are also included — see the tool list below.)

Its toolset

Everything the assistant can do here goes through one of these:

• Success — { ok: true, ts, meta, data }
• Error — { ok: false, ts, meta, error }, where error includes:
• code — stable string (prefer API code, otherwise inferred)
• httpStatus — HTTP status when the failure came from an API call
• requestId — request/correlation id if returned by API
• hint — 1-line “what to do next”
• Cursor — Use the **[Add to Cursor](https://cursor.com/en/install-mcp?name=ethora&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBldGhvcmEvbWNwLXNlcnZlciJdfQ%
• Windsurf — The Windsurf tool exposed by this server
• Cline — Open the MCP servers panel and edit cline_mcp_settings.json:

Configuration

You will need 3 environment variables: ETHORA_B2B_TOKEN, ETHORA_API_URL, ETHORA_BASE_URL. 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.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ethora MCP Cli's toolset — Success, Error, code and 6 more — is a fair guide to whether it matches your workflow. It is maintained by dappros; 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.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ethora MCP Cli.
• 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 ethora mcp cli mcp server does with a few real requests.