MCP server

The MCP server wraps /api/v1 so Cursor, Claude Code, and other MCP clients can manage apps and servers.

Install

Published as @21tycoons/tycoonbox-mcp. No local install required — npx fetches it on first use.

Cursor config

{
  "mcpServers": {
    "tycoonbox": {
      "command": "npx",
      "args": ["-y", "@21tycoons/tycoonbox-mcp"],
      "env": {
        "TYCOONBOX_API_TOKEN": "your-token",
        "TYCOONBOX_API_URL": "https://panel.example.com"
      }
    }
  }
}

Generate a token under Settings → API access with the scopes you need. write covers app mutations (exec, env, config) but not deploy, webhooks, server infra, or team admin — add deploy, servers, and/or admin explicitly. For MCP with full panel control, select all scopes (or at minimum what your workflow needs).

No git OAuth: ship with POST /api/v1/projects/upload (multipart zip) or POST /api/v1/projects with a public git HTTPS URL and deploy_now=true (needs deploy scope). Replace an upload app’s zip with POST /api/v1/projects/:id/replace_upload. MCP tools: upload_project, replace_project_upload (pass file_path or archive_base64 + filename). See API.md.

Tools (v0.6.0)

Full Hatchbox-style coverage — one tool per API operation. See mcp/README.md for the complete list (60+ tools across apps, deploys, env, domains, processes, cron, servers, databases, backups, and mail).

Marketing page: /mcp on your panel host.

Publish

Maintainers with npm access to the @21tycoons scope:

DRY_RUN=1 scripts/publish-mcp.sh
scripts/publish-mcp.sh