Ethora Mcp Server
Wire your coding agent into Ethora chat, messaging automation, RAG, and in-app AI agents without hand-rolling REST calls.
Overview
Ethora MCP server is a Build-phase MCP server for the integrations subphase that exposes Ethora chat, messaging, RAG, and automation APIs to AI coding agents.
What is this MCP server?
- stdio MCP package @ethora/mcp-server (v26.5.3) for Claude Code, Cursor, and other MCP clients
- Configure ETHORA_API_URL or ETHORA_BASE_URL plus optional ETHORA_APP_JWT and ETHORA_B2B_TOKEN for user and tenant auth
- Runtime configuration via ethora-configure when secrets are not in environment variables
- Chat ops, AI agents, RAG, and messaging automation against the Ethora platform API
- Defaults to https://api.chat.ethora.com/v1 when base URL env vars are unset
- Package version 26.5.3 on npm as @ethora/mcp-server
- Transport: stdio
- Default API base resolves to https://api.chat.ethora.com/v1 when env URLs are omitted
Community signal: 6 GitHub stars.
What problem does it solve?
You are building on Ethora but your agent cannot safely call chat, auth, and automation endpoints without a maintained integration layer.
Who is it for?
Indie builders already on Ethora who want agent-driven chat workflows, RAG, or B2B tenant automation during feature development.
Skip if: Teams that only need a public website chat widget with no Ethora tenant, or builders who want a single skill file instead of a live API MCP bridge.
What do I get? / Deliverables
After registration, your agent can configure Ethora credentials and perform chat ops and automation through typed MCP tools instead of ad-hoc HTTP scripts.
- Registered stdio MCP server the agent can invoke for Ethora chat and automation tools
- Documented env-based or runtime ethora-configure credential setup
- Agent-callable Ethora API operations without custom HTTP glue in every task
Recommended MCP Servers
Journey fit
Ethora is a product integration layer you add while building chat-centric or agent-backed features, not a launch or growth tactic. Canonical shelf is integrations because the server exposes Ethora API auth (app JWT, B2B token) and chat or automation tools over stdio MCP.
How it compares
Live Ethora API bridge over MCP, not a static Claude skill for prompt-only chat design.
Common Questions / FAQ
Who is io.github.dappros/ethora-mcp-server for?
It is for solo and small-team developers building on the Ethora messaging platform who want their Claude Code, Cursor, or Codex agent to run chat and automation against real Ethora APIs.
When should I use io.github.dappros/ethora-mcp-server?
Use it during the build phase when you are wiring agent tooling or backend integrations for Ethora-hosted chat, AI agents, or RAG-backed messaging features.
How do I add io.github.dappros/ethora-mcp-server to my agent?
Install @ethora/mcp-server from npm, set ETHORA_API_URL or ETHORA_BASE_URL and the appropriate JWT or B2B token env vars, then add the stdio MCP server entry in your agent’s MCP configuration.