golive-mcp

Go Live — deploy from your AI agent in one command.

Works with Claude Code, Cursor, Gemini CLI, Copilot CLI, or any MCP-compatible client.

What is this?

Go Live is an MCP server that gives your AI agent superpowers: create a GitHub PR, deploy to production, and verify it's live — all from a single natural language request.

No YAML pipelines. No CI/CD config. Just tell your AI "deploy this" and it happens.

Why

Production deploys are the most error-prone part of AI-assisted coding. Write code, commit, push, create a PR, build, upload, copy files, restart, check if it's live — that's 9+ manual steps, and most AI coding agents stop at "here's your code," leaving deploy as homework. Go Live turns the whole sequence into one sentence: "deploy to production."

Quick Start

# Run directly — no install needed
npx github:abbylester1/golive-mcp

# Or install globally
npm install -g github:abbylester1/golive-mcp
golive-mcp

Create a deploy.config.json in your project root, then tell your AI:

"Deploy to production"

Use Cases

Installation

# Run without installing
npx github:abbylester1/golive-mcp

# Or install globally
npm install -g github:abbylester1/golive-mcp
golive-mcp

MCP Client Setup

claude mcp add golive-mcp -- npx github:abbylester1/golive-mcp

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "golive-mcp": {
      "command": "npx",
      "args": ["github:abbylester1/golive-mcp"],
      "env": {}
    }
  }
}

Add to .vscode/mcp.json:

{
  "servers": {
    "golive-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["github:abbylester1/golive-mcp"]
    }
  }
}

opencode mcp add golive-mcp -- npx github:abbylester1/golive-mcp

What it does

Three tools your AI can call:

create_pr

Create a GitHub PR from your current branch.

{
  "title": "Fix login bug",
  "body": "Closes #42",
  "base": "main",
  "commitMessage": "fix: login redirect"
}

If commitMessage is set, it auto-commits everything. Just need gh CLI installed.

deploy

Build and deploy to production (or any target you've configured).

{
  "target": "production",
  "skipBuild": false
}

Works with any hosting provider.

status

Check if your site is live.

{
  "target": "production"
}

Hits your health check URL and reports back what it got.

Hosting you can deploy to

If Go Live doesn't have a built-in provider for your host, use the custom provider — it runs any shell commands you want.

Spaceship (cPanel shared hosting)

Go Live is the only MCP deploy tool that handles Spaceship's CageFS setup:

{
  "targets": {
    "production": {
      "provider": "spaceship",
      "build": { "command": "npm run build", "cwd": "frontend" },
      "spaceship": {
        "host": "server43.shared.spaceship.host",
        "user": "user@domain.com",
        "password": "",
        "remotePath": "/app",
        "cageFsPath": "/home/user/domain.com/kyro/app",
        "phpCopyUrl": "https://domain.com/deploy.php"
      },
      "healthCheckUrl": "https://domain.com/api/health"
    }
  }
}

Custom (any host not listed)

{
  "targets": {
    "production": {
      "provider": "custom",
      "build": { "command": "npm run build", "cwd": "." },
      "custom": [
        "rsync -avz --delete out/ user@host:/var/www/html/",
        "ssh user@host 'systemctl reload nginx'"
      ],
      "healthCheckUrl": "https://mysite.com/api/health"
    }
  }
}

Configuration

Create deploy.config.json in your project root (or Go Live finds it here):

1. deploy.config.json in current directory

2. deploy.json in current directory

3. ~/.config/golive-mcp/config.json

4. --config=/path/to/config.json flag

⚠️ deploy.config.json holds real credentials (FTP/cPanel passwords, Vercel/cloud tokens). It's already in .gitignore - never remove that entry or commit a filled-in config. For a shared machine or CI, prefer option 3 (~/.config/golive-mcp/config.json) so secrets never live inside a repo at all.

How it's different

License

MIT