MCP

Drive Nodion from your coding agent.

Nodion hosts a remote Model Context Protocolserver. Your agent uses the same account you use in the dashboard: create a project, deploy an app, set env vars, read logs, without a local daemon.

Server: https://mcp.nodion.net (Claude Desktop: https://mcp.nodion.net/mcp)
One-click setup for Cursor, Claude Code, and Claude Desktop: Connect Nodion to your agent

Authenticate

New account? Tell the agent to follow auth.md or run nodion login. You approve in the browser. The CLI stores a personal key in ~/.config/nodion/config.yml — do not paste that token into chat.

For MCP, create a personal key under Account → Security (shown once) and set Authorization: Bearer nodion_…. Do not copy the CLI config file into chat.

OpenCode

OpenCode has its own config format. Add Nodion to opencode.json:

json{
  "mcp": {
    "nodion": {
      "type": "remote",
      "url": "https://mcp.nodion.net",
      "headers": {
        "Authorization": "Bearer nodion_…"
      }
    }
  }
}

Any other client

Windsurf, Zed, VS Code Copilot, and custom agents can use the same URL. A typical config:

json{
  "mcpServers": {
    "nodion": {
      "url": "https://mcp.nodion.net",
      "headers": {
        "Authorization": "Bearer nodion_…"
      }
    }
  }
}

What the agent can do

Once connected, ask in plain language. Typical work: create a project, deploy an app from the current repo, attach a database, set environment variables, read logs, and check that a release is live. Write actions ask you to confirm before they run.

A local agent with a shell and network (Cursor or Claude Code, API key from Account → Security) can deploy a folder that is not a Git repository: apps.create with source_kind=managed_git (the create response has no push URL or password), then the agent calls apps.git_remote itself (the dashboard does not show the password; each call issues a new one and revokes the previous one), then git push with GIT_ASKPASS (do not put the password in the URL, .git/config, argv, shell history, logs, or chat), then deploy. Hosted ChatGPT/OAuth does not get apps.git_remote (there is no connector or dashboard toggle for it). Those clients can still ship HTML/CSS/JS from the chat: apps.create with source_kind=managed_git and deployment_strategy=buildpacks, then apps.git_files, then deploy. A local folder on disk still needs Cursor or Claude Code with a write key. Connected GitHub remains an option when the user already has a repo.

ChatGPT, Codex, and Claude Desktop

ChatGPT, Codex, and Claude Desktop (claude.ai, mobile, Cowork) use OAuth, not an API key. Sign in or create an account on the Nodion authorize page, bind one or more projects, then deploy HTML/CSS/JS from the chat with apps.git_files, or from a Git repository you have already connected. Secrets stay in the dashboard; the connection does not collect passwords or environment values in chat. Hosted Claude connectors are brokered by Anthropic.

Cursor and Claude Code still need a key from Account → Security. ChatGPT, Codex, and Claude Desktop open an account on the authorize page.