Ethora MCP Server logo

Ethora MCP Server

Connects AI clients to Ethora for chat operations, app management, agents, RAG indexing, and widget embeds.

Install Ethora MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ethora-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ethora/mcp-server"
      ],
      "env": {
        "ETHORA_API_URL": "YOUR_VALUE_HERE",
        "ETHORA_APP_JWT": "YOUR_VALUE_HERE",
        "ETHORA_B2B_TOKEN": "YOUR_VALUE_HERE",
        "ETHORA_MCP_AUTH_ISSUER": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 89 tools correctly (1mo ago).

Overview

The ethora-mcp-server MCP server exposes Ethora chat and messaging operations as MCP tools for AI clients and autonomous agents. It supports hosted HTTP, self-hosted HTTP, and local stdio deployments, with authentication through API keys, OAuth, user login, app tokens, or B2B tokens depending on the entry point. Agents can manage Ethora apps, rooms, users, and AI agents, post messages, index RAG sources, and generate website chat-widget embeds. Use it when an agent needs to operate an Ethora installation or connect conversations and automation to Ethora.

Use cases

  • Manage Ethora apps and chat rooms through agent tool calls
  • Post messages and automate Ethora conversations
  • Create and configure Ethora AI agents
  • Index sources for retrieval-augmented generation
  • Generate website chat-widget embeds

Key features

  • Hosted, self-hosted, and stdio deployment modes
  • API key, OAuth 2.1, user, app, and B2B authentication
  • Ethora app, room, user, and agent management
  • Message posting and RAG source indexing
  • API key lifecycle management
  • Website chat-widget embed generation

Tools89

What Ethora MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~24.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · @ethora/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed89Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Ethora MCP Server works

What ethora-mcp-server MCP server does

The ethora-mcp-server MCP server connects MCP-compatible clients and autonomous agents to Ethora, an open-source chat and messaging platform with an AI agent framework. Tool calls can create and manage Ethora applications, chat rooms, users, and AI agents. Agents can also post messages, index sources for retrieval-augmented generation, and create website chat-widget embed output.

The server includes session and authentication utilities for checking status, selecting an authentication mode, logging users in or registering them, configuring local credentials, and managing API keys. ethora-help reads the current session state and suggests the next calls, while ethora-status and ethora-doctor provide operational information.

How it works

Three deployment modes are documented:

  • Hosted Ethora Cloud at https://mcp.chat.ethora.com/mcp.
  • Self-hosted deployment included with the Ethora monoserver.
  • A local stdio process started with npx -y @ethora/mcp-server.

Hosted and self-hosted deployments use HTTP transport. The hosted service also provides /mcp/k/<api-key> for personal connector URLs and /mcp/oauth for OAuth 2.1 clients. A personal connector URL embeds the API key, while other HTTP clients can send a Bearer token in the request header. OAuth clients obtain access tokens from the Ethora authorization server and use scopes such as read, write, and admin.

Each MCP session keeps private in-memory state, including the selected app and authentication tokens. The documented stdio flow uses an Ethora API URL and an app JWT to bootstrap access. A B2B token can also be supplied for server integrations.

Setup and configuration

For Claude.ai or ChatGPT custom connectors, create an API key in the Ethora web app under Account and AI Assistants, then use the personal connector URL shown there. The hosted OAuth URL is available for clients that perform the vendor login flow. Cursor, VS Code, Claude Code, and clients that accept an MCP URL are also documented connection options.

For a local process, configure the server with ETHORA_API_URL and ETHORA_APP_JWT, then launch the npm package. After connecting, an agent can call ethora-status, authenticate with ethora-user-login or ethora-user-register, and list applications with ethora-app-list. Self-hosted OAuth requires ETHORA_MCP_AUTH_ISSUER to identify the public Ethora API authorization server.

Tools and capabilities

The ethora-mcp-server MCP server supports capabilities for:

  • Creating and managing Ethora apps, rooms, users, and AI agents.
  • Posting messages and performing chat operations.
  • Indexing RAG sources.
  • Producing website chat-widget embeds.
  • Registering and logging in users.
  • Creating, listing, and revoking API keys.
  • Inspecting connection state and getting setup guidance.

API keys are displayed only when created. A key can act as the associated user and should be treated like a password. Revoking a key invalidates it for subsequent requests.

Limitations and notes

App-token and B2B authentication modes are intended for server integrations, while agents and rooms routes reject app tokens. OAuth access is controlled by tool scopes: read-only operations require read, destructive operations require admin, and other operations require write. Identity-management tools are hidden on the OAuth endpoint because the OAuth token already determines the user.

The hosted service is available at production and QA URLs documented by the project. Personal connector URLs contain credentials and should not be shared. The project specifies Node.js version 18 or later for the package-based setup.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ethora MCP Server

Use the hosted MCP endpoint without a local install, deploy it with an Ethora monoserver, or run `npx -y @ethora/mcp-server` for the stdio mode.

Yes.

Use a personal API-key connector URL, a Bearer token, OAuth 2.1, or the stdio environment variables. Hosted sessions can also call the user login or registration tools.

Yes. Its documented tools can create and manage Ethora apps, chat rooms, users, and AI agents, as well as post messages.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewEthora MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ethora-mcp-server?style=directory)](https://allmcps.com/mcp/ethora-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/ethora-mcp-server"><img src="https://allmcps.com/api/badge/ethora-mcp-server?style=directory" alt="Ethora MCP Server on AllMCPs" /></a>