Install the Eden MCP from the command line

Most people should still use the buttons in Eden → Settings → Integrations. Those use OAuth, open a browser sign-in flow, and are easiest for Claude, Cursor, and ChatGPT.

Use the CLI when you want to configure a local MCP client directly, set up a managed machine, repair a config file, or avoid clicking through client settings.

What you'll need

• Node.js installed locally.
• An Eden personal access token from Settings → Integrations → API access.
• Cursor or Claude Desktop installed on the machine you are configuring.

Install Cursor from the CLI

Run:

npx eden-mcp setup --client cursor

The CLI asks for your Eden token, updates Cursor's MCP config, and tests the connection. By default, it writes to:

~/.cursor/mcp.json

After setup, restart or refresh Cursor's MCP tools if Cursor does not show Eden right away.

Install Claude Desktop from the CLI

Run:

npx eden-mcp setup --client claude-desktop

Claude Desktop expects local stdio MCP servers, so the CLI configures Eden through mcp-remote. That bridge lets Claude Desktop talk to Eden's hosted MCP endpoint.

On macOS, the CLI writes to:

~/Library/Application Support/Claude/claude_desktop_config.json

Restart Claude Desktop after setup so it reloads the config.

Test an existing connection

To check that your token and Eden's MCP endpoint are working:

npx eden-mcp test

The test lists Eden's tools and calls a lightweight workspace endpoint. If the token is expired, revoked, or missing the right access, the CLI will tell you before you open your AI client.

Useful flags

npx eden-mcp setup --client cursor --dry-run
npx eden-mcp setup --client claude-desktop --server-name eden-work
npx eden-mcp setup --client cursor --config ~/custom/mcp.json
npx eden-mcp print-config --client claude-desktop

• --dry-run previews the Eden config without writing a file.
• --server-name changes the MCP server name, useful if you already have an eden entry.
• --config writes to a custom MCP config file.
• print-config prints the config snippet so you can paste it into another client.

How this differs from the in-app buttons

The in-app buttons use OAuth: the client opens Eden in a browser, you sign in, and Eden issues the assistant a connection. That is the best experience for most users.

The CLI uses a personal access token. That makes it better for local config files, managed devices, and clients that do not have a clean OAuth install flow. Keep the token private. Anyone with it can access Eden with the scope you granted.

Uninstall or reconnect

To remove Eden, delete the eden entry from your client's MCP config file. To rotate access, revoke the token in Settings → Integrations → API access, generate a new one, and run setup again.

If you would rather use browser sign-in, go back to Settings → Integrations and click the assistant-specific setup button instead.