Get a token

24 of the 25 tools act on your account, so they need an API token. Create one in the dashboard:

1. 1. Sign in, then click your avatar in the top right and choose API tokens.
2. 2. Give the token a name you will recognise later, like claude-desktop.
3. 3. Choose its scopes. See below.
4. 4. Copy it. It is shown once and stored hashed, so if you lose it you create another.

Which scope

Give a token the least it needs. The API enforces this, so a read-only token cannot deploy even if an agent asks it to.

Install and connect

The server is a small Node process that your MCP client starts for you. Build it once, then point your client at the absolute path to dist/index.js.

npm install && npm run build

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows, then restart Claude.

{
  "mcpServers": {
    "eigon": {
      "command": "node",
      "args": ["/absolute/path/to/eigon-mcp/dist/index.js"],
      "env": { "EIGON_TOKEN": "eigon_ab12cd_xxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

Claude Code

claude mcp add eigon \
  --env EIGON_TOKEN=eigon_ab12cd_xxxxxxxxxxxxxxxxxxxxxx \
  -- node /absolute/path/to/eigon-mcp/dist/index.js

Cursor

Settings, then MCP, then add a server with the same command, args and env as the Claude Desktop block above.

Settings

Your first ask

Once it is connected, talk to your assistant normally. Things that work on the first try:

• No account needed: “Would github.com/gothinkster/realworld deploy on Eigon, and what would it cost a month?”
• “List my Eigon projects and tell me which environments are running.”
• “Deploy my staging environment and tell me when it is live.”
• “My app returns 500s. Read the logs and tell me what broke.”
• “Pause my dev environment until Monday, keep the database.”

A first deploy into a fresh environment provisions a network, a cluster and a load balancer, which takes minutes rather than seconds. The tool descriptions say so, so a well-behaved agent waits instead of deciding it has hung.

Every tool

You never call these yourself; your assistant picks from them. They are listed so you can see exactly what you are handing it.

What it will not do

An agent acting on a loosely worded instruction is the case worth designing for, so some things are deliberately absent.

• There is no delete tool. eigon_teardown_preview tells an agent exactly what deleting an environment would destroy, and a person runs the deletion. An agent that can irreversibly drop your database on a misread sentence is not a feature.
• Pause keeps your data. eigon_pause snapshots databases and keeps them unless it is explicitly told otherwise. The destructive option has to be asked for by name.
• Secrets only go in. eigon_list_secrets returns names, never values. Nothing in Eigon can read a secret back out, including this server.
• A token cannot widen itself. A deploy token cannot create another token, so an agent cannot grant itself more access than you gave it.

Troubleshooting

The tools do not appear in my client

Restart the client after editing its config. An MCP server is started once when the client launches, so a config change does nothing until it restarts. Check the path in args is absolute and that dist/index.js exists, which means npm run build has been run.

Every tool says it is not authenticated

EIGON_TOKEN is missing or expired. Tokens can be given an expiry, and a revoked token stops working immediately. Create a new one from the avatar menu, then restart the client.

Reading works, deploying is refused

The token has read but not deploy. Scopes cannot be changed after a token is created, so make a new one.

It deployed and the app is still down

Ask for eigon_logs. A deploy can succeed while the container crashes on start, and the logs name the reason. Eigon reads the container’s own crash output rather than the build log, so the answer is usually one line.