Ethora Mcp Server

Please install the `ethora-mcp-server` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 18+** — Node.js is required to run the MCP server via npx. The README recommends version 18.x or higher.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@ethora/mcp-server"]
- optional environment variables:
  - `ETHORA_API_URL`: Full Ethora API URL to send requests to. If set, this takes precedence over ETHORA_BASE_URL. (example: `<your-ethora-api-url>`)
  - `ETHORA_BASE_URL`: Base Ethora host URL. If provided, the server defaults to appending /v1. (example: `<your-ethora-base-url>`)
  - `ETHORA_APP_JWT`: App JWT used for login/register bootstrap in user-auth mode. (example: `<your-app-jwt>`)
  - `ETHORA_B2B_TOKEN`: B2B server token used for tenant-actor server-to-server flows via x-custom-token auth. (example: `<your-b2b-token>`)
  - `ETHORA_MCP_ENABLE_DANGEROUS_TOOLS`: Set to true to expose destructive tools such as app deletion, wallet transfer, and bulk delete tools. (example: `<true-or-false>`)

Note: The server runs over stdio. Credentials can also be set at runtime with the ethora-configure tool, but the README recommends env vars or client secret stores for secrets because tool arguments may end up in transcripts. No auth env vars are universally required for startup: ethora-doctor works without credentials, while user-auth flows typically need ETHORA_APP_JWT and B2B flows typically need ETHORA_B2B_TOKEN.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.