INDIVIDUAL MCP TOOL

fetch

Fetch the full text of a documentation section or tool reference entry by the id returned from `search` (e.

ethora.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.chat.ethora.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for fetch and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ethora-mcp-server]
url = "https://mcp.chat.ethora.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "ethora-mcp-server": {
      "type": "http",
      "url": "https://mcp.chat.ethora.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: ethora-mcp-server
Remote MCP URL: https://mcp.chat.ethora.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ethora-mcp-server": {
      "url": "https://mcp.chat.ethora.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "ethora-mcp-server": {
      "type": "http",
      "url": "https://mcp.chat.ethora.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "ethora-mcp-server",
  "transport": "streamable-http",
  "url": "https://mcp.chat.ethora.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ethora-configure — Set the Ethora API URL and credentials for this MCP session.
ethora-status — Report the current Ethora MCP session state: configured API URL, active auth mode, which credentials are present (booleans like `hasAppJwt` — values never echoed), the selected appId/agentId, and `hosted`/`sessionId` on the hosted (Streamable HTTP) server.
ethora-help — Task-oriented orientation for this MCP server: explains the three Ethora auth modes (user / app-token / B2B) and recommends next tool calls + recipes based on current session state.
ethora-run-recipe — Execute a built-in recipe — an ordered sequence of this server's own tool calls — by id.
ethora-doctor — Diagnose the session: validate the config is internally consistent for the active auth mode and ping the Ethora API (`GET /v1/ping`).
ethora-auth-use-app — Switch this session's active auth mode to app-token, so subsequent app-scoped calls authenticate with the configured `appToken`.
ethora-auth-use-user — Switch this session's active auth mode to user-session, so subsequent calls authenticate as a logged-in Ethora user.
ethora-auth-use-b2b — Switch this session's active auth mode to B2B, so subsequent calls authenticate as a tenant actor via the `x-custom-token` header.