Ethora MCP server for Cursor, VS Code, Windsurf and Cline

Get a key

In the Ethora web app open Account, AI Assistants and create an API key; the page shows a Cursor config with a copy button. Keys default to 90 days, max 365, value shown once. No account? Register or let the assistant call ethora-user-register on the open endpoint.

Cursor

Put the block in .cursor/mcp.json at the project root or ~/.cursor/mcp.json for every project; servers are managed from the Customize panel. Cursor asks for approval before using MCP tools by default. The same block works for Windsurf (~/.codeium/windsurf/mcp_config.json), Cline (cline_mcp_settings.json, opened from the MCP Servers icon) and Gemini CLI (~/.gemini/settings.json).

{
  "mcpServers": {
    "ethora": {
      "url": "https://mcp.chat.ethora.com/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

VS Code and GitHub Copilot agent mode

Create .vscode/mcp.json; the top-level key is servers, not mcpServers, and remote servers declare "type": "http". The MCP: Add Server command fills the same fields at workspace or user level. Tools appear behind the Configure Tools button in the chat input, where you can toggle them; you may be asked to confirm each invocation.

{
  "servers": {
    "ethora": {
      "type": "http",
      "url": "https://mcp.chat.ethora.com/mcp",
      "headers": { "Authorization": "Bearer <your API key>" }
    }
  }
}

Or one-click install the stdio package

The GitHub README has Add to Cursor and Install in VS Code buttons that register npx -y @ethora/mcp-server as a local stdio server. Supply credentials through environment variables or ethora-configure at runtime for a quick test.

{ "mcpServers": { "ethora": { "command": "npx", "args": ["-y", "@ethora/mcp-server"] } } }

# credentials, if you run it by hand
ETHORA_API_URL=https://api.chat.ethora.com/v1 ETHORA_APP_JWT="JWT <your app jwt>" npx -y @ethora/mcp-server

Try it

Open the chat in agent mode and ask for a documentation lookup first (search and fetch need no login), then something real. ethora-status should report authMode: user; when unsure of the call order the assistant runs ethora-help.

Remote or stdio?

Remote when you want no local process, revocable keys and OAuth for shared setups. Stdio when the machine cannot hold a personal key (CI), when you point ETHORA_API_URL at a self-hosted Ethora API, or when you need ETHORA_B2B_TOKEN for server-side provisioning. Same tools; app deletion on stdio needs ETHORA_MCP_ENABLE_DANGEROUS_TOOLS=true.