Developer tools

Connect coding agents

Wire your AI coding agent — Claude Code, Cursor, Windsurf, or anything that speaks MCP — straight to Orizon. Your agent can then create projects, deploy, read logs, and manage env and databases on your behalf.

One-click MCP

The Orizon CLI ships an MCP server you run over stdio: orizon mcp. It authenticates with your platform API key from the ORIZON_API_KEY environment variable. Install the CLI first:

shell

curl -fsSL https://cdn.orzn.space/cli/install.sh | sh

Claude Code

One command registers the server:

shell

claude mcp add orizon --env ORIZON_API_KEY=orz_pk_xxx -- orizon mcp

Generic MCP config (Cursor, Windsurf, others)

Any MCP client takes the same shape. Add this to the client's MCP config:

shell

{
  "mcpServers": {
    "orizon": {
      "command": "orizon",
      "args": ["mcp"],
      "env": { "ORIZON_API_KEY": "orz_pk_xxx" }
    }
  }
}

The config file location differs per client:

shell

Cursor    ~/.cursor/mcp.json            (or .cursor/mcp.json in a project)
Windsurf  ~/.codeium/windsurf/mcp_config.json
Claude    via "claude mcp add" (above) or ~/.claude.json

Keep your key safeUse a scoped platform key from dashboard.orizon.ng/api-keys. A read key lets an agent inspect projects and logs without being able to deploy or change anything; a full key lets it deploy and manage. The secret is shown once.

Available MCP tools

The server exposes these tools to your agent:

list_projectsList your projects

get_projectGet one project's details

create_projectCreate a new project

deploy_projectTrigger a deployment

list_deploymentsList a project's deployments

get_deploymentGet a deployment's status

get_deployment_logsRead a deployment's logs

list_envList environment variables

set_envSet environment variables

list_databasesList managed databases

get_databaseGet one managed database

list_domainsList a project's domains

list_emailsList recent transactional emails

AGENTS.md for your repo

Drop an AGENTS.md into your repository so any coding agent — even one without the MCP server — learns how to deploy this project to Orizon. Copy the template below, or grab the hosted one at orzn.io/AGENTS.md.

shell

# Orizon deployment

This project deploys to **Orizon** (https://orzn.io).

## Install the CLI
```sh
curl -fsSL https://cdn.orzn.space/cli/install.sh | sh
```

## Authenticate
Create a platform API key at https://dashboard.orizon.ng/api-keys
(it looks like `orz_pk_...`), then either:
```sh
orizon login --key orz_pk_xxx
# or, for CI / agents:
export ORIZON_API_KEY=orz_pk_xxx
```

## Deploy
```sh
orizon link --project <proj_id>   # once, links this dir to a project
orizon deploy                     # zip cwd, upload, deploy, stream logs
```

## Useful commands
```sh
orizon logs --follow      # stream the latest deployment's logs
orizon env pull           # print this project's env vars
orizon env push .env      # set env vars from a file (triggers a redeploy)
orizon open               # open the live URL
```

## Notes
- Server apps MUST listen on the port from `PORT` (Orizon runs with PORT=3000).
- Static sites and PHP apps are served directly (no PORT needed).
- Docs: https://orzn.io/docs   ·   Machine docs: https://orzn.io/llms.txt

Machine-readable docs

Point your agent at Orizon's agent-readable docs for context:

shell

https://orzn.io/llms.txt        # index of every doc page
https://orzn.io/llms-full.txt   # core docs in one file
https://orzn.io/AGENTS.md       # drop-in repo template

CLI

The commands the MCP server wraps.

API keys

Create and scope the key your agent uses.