Orgo MCP Server

Official MCP server for controlling Orgo cloud computers from Claude Code, Claude Desktop, and other Model Context Protocol clients.

This package is TypeScript-first and ships as @orgo-ai/mcp.

Quick Start

1. Get an Orgo API key

Sign up or log in at orgo.ai, then copy an API key from Settings > API Keys.

2. Add the MCP server

Claude Code:

claude mcp add orgo -e ORGO_API_KEY=sk_live_YOUR_KEY -- npx -y @orgo-ai/mcp

Claude Desktop:

{
  "mcpServers": {
    "orgo": {
      "command": "npx",
      "args": ["-y", "@orgo-ai/mcp"],
      "env": {
        "ORGO_API_KEY": "sk_live_YOUR_KEY"
      }
    }
  }
}

Hosted Streamable HTTP server:

{
  "mcpServers": {
    "orgo": {
      "type": "http",
      "url": "https://orgo-mcp.onrender.com/mcp",
      "headers": {
        "X-Orgo-API-Key": "${ORGO_API_KEY}"
      }
    }
  }
}

PowerShell users can wrap the Claude Code command because PowerShell may mangle -- when it reaches npm shims:

cmd /c "claude mcp add orgo -e ORGO_API_KEY=sk_live_YOUR_KEY -- npx -y @orgo-ai/mcp"

Tools

The server exposes 24 focused tools.

Each tool is registered with MCP annotations for readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. orgo_restart_computer is marked destructive because it can interrupt running processes and unsaved VM state. Text responses are sanitized before they are returned to the MCP client, so password, token, secret, credential, and API-key fields are redacted even when Orgo API responses include them.

Deliberately not exposed:

• computer start/stop tools

• VNC password access

• account/profile/credits/transactions

• autonomous agent/thread tools

• RTMP streaming tools

• template management tools

Production Safety Controls

Use environment variables to restrict the exposed surface without changing client config.

Examples:

# Observation-only mode
ORGO_READ_ONLY=true npx -y @orgo-ai/mcp

# Browserless VM control without shell access
ORGO_TOOLSETS=core,screen,files npx -y @orgo-ai/mcp

# Keep shell enabled, but remove bash
ORGO_TOOLSETS=shell ORGO_DISABLED_TOOLS=orgo_bash npx -y @orgo-ai/mcp

Read-only mode currently exposes:

orgo_list_workspaces
orgo_get_workspace
orgo_workspace_by_name
orgo_list_computers
orgo_get_computer
orgo_screenshot
orgo_list_files
orgo_download_file

Environment Variables

Self-Hosting

Local stdio:

git clone https://github.com/nickvasilescu/orgo-mcp.git
cd orgo-mcp
npm install
ORGO_API_KEY=sk_live_YOUR_KEY npm start

Local HTTP:

npm install
npm run build
MCP_TRANSPORT=http npm start
curl http://localhost:8000/health

Docker:

docker build -t orgo-mcp .
docker run -p 8000:8000 -e MCP_TRANSPORT=http orgo-mcp

Render:

1. Fork this repo.

2. Create a Render Blueprint from render.yaml.

3. Connect clients to https://YOUR_RENDER_HOST/mcp with an X-Orgo-API-Key header.

The hosted server does not store a shared Orgo key. Each request must include the user's Orgo API key header.

Architecture

npx / stdio:
  MCP client -> stdio -> @orgo-ai/mcp -> Orgo API
                           ORGO_API_KEY env var

Hosted HTTP:
  MCP client -> HTTPS -> orgo-mcp server -> Orgo API
                          X-Orgo-API-Key header

Shell commands:
  orgo_bash -> Terminal WebSocket primary -> VM
            -> REST /bash fallback        -> VM

Development

npm install
npm run build
npm test
npm start

CI runs:

• TypeScript build from a clean dist/

• MCP tool-list smoke tests for default, read-only, toolset, allowlist, and denylist policies

• HTTP transport health and auth smoke tests

• npm package content checks

• Docker image build

Before publishing:

npm test
npm pack --dry-run

Troubleshooting

Security

• Do not commit .env files or API keys.

• Prefer ORGO_READ_ONLY=true for observation-only clients.

• Disable the shell toolset for clients that should not execute VM commands.

• Treat orgo_bash and orgo_exec as high-power tools: they can modify anything reachable from the target VM.

• HTTP deployments should pass the user's key per request via X-Orgo-API-Key; do not bake a production Orgo key into the server.

License

MIT. See LICENSE.