🚀 otoinstall-mcp-server

Deploy projects from any AI tool with a single command.

Works with Claude Desktop, Cursor, Windsurf, Cline, Continue, Zed, Roo Code, Antigravity, Amazon Q, and any MCP-compatible AI assistant.

Quick Start

1. Get Your API Key

Sign up at otoinstall.com → Dashboard → API Keys → Create Key

2. Configure Your AI Tool

Choose your tool below and add the configuration:

🤖 Claude Desktop

Edit claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

🖱️ Cursor

Settings → MCP Servers → Add:

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

Or via .cursor/mcp.json in your project root.

🏄 Windsurf

Settings → MCP → Add server:

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

🔌 Cline (VS Code Extension)

Cline settings → MCP Servers → Add:

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

➡️ Continue (VS Code / JetBrains)

Edit ~/.continue/config.json:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "otoinstall-mcp-server"],
          "env": {
            "OTOINSTALL_API_KEY": "oi_live_your_key_here"
          }
        }
      }
    ]
  }
}

⚡ Zed

Edit ~/.config/zed/settings.json:

{
  "context_servers": {
    "otoinstall": {
      "command": {
        "path": "npx",
        "args": ["-y", "otoinstall-mcp-server"],
        "env": {
          "OTOINSTALL_API_KEY": "oi_live_your_key_here"
        }
      }
    }
  }
}

🦘 Roo Code

.roo/mcp.json:

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

🔧 Antigravity (Google Gemini)

Add to your MCP configuration:

{
  "mcpServers": {
    "otoinstall": {
      "command": "npx",
      "args": ["-y", "otoinstall-mcp-server"],
      "env": {
        "OTOINSTALL_API_KEY": "oi_live_your_key_here"
      }
    }
  }
}

🏗️ Any MCP-Compatible Tool

The universal configuration pattern:

{
  "command": "npx",
  "args": ["-y", "otoinstall-mcp-server"],
  "env": {
    "OTOINSTALL_API_KEY": "oi_live_your_key_here",
    "OTOINSTALL_BASE_URL": "https://otoinstall.com"
  }
}

🛠️ Available Tools (9 total)

| Tool | Description | |---|---| | analyze_project | Required first — Analyze project type, dependencies, and compatibility | | deploy_project | Zip & deploy a project directory to a live server | | deploy_zip | Deploy an existing ZIP file | | check_deploy_status | Check deployment progress and status | | get_deploy_logs | View detailed deployment logs | | list_projects | List all your deployments | | list_servers | List configured server credentials | | add_server | Save new FTP/SFTP/SSH server credentials | | whoami | Check API key owner and permissions |

💬 Usage Examples

Deploy from Claude / Cursor / Any AI

You: "Deploy this project to my server"
AI:  I'll deploy the project. First, let me check your servers.
     [calls whoami → verifies account]
     [calls list_servers → finds saved servers]
     
     You have 1 server: [ID: 1] MyVPS — sftp://[email protected]
     
     [calls analyze_project → analyzes code]
     📋 Project Analysis:
        ⚙️ Technology: React (Vite)
        🗄️ Database: None
        🔨 Build: Yes (Vite)
        ✅ Shared hosting compatible: Yes
     
     Ready to deploy? (yes/no)

You: "yes"
AI:  [calls deploy_project with analysis_confirmed=true]
     ✅ Deployment started! Deploy ID: 01HYJ3R8KQ...
     [calls check_deploy_status]
     🎉 Deployment completed! Your site is live at https://mysite.com

First-Time User (No Server Saved)

You: "Deploy this to production"
AI:  [calls list_servers → empty]
     You don't have any servers saved. Let me help you set one up.
     Do you have a domain and hosting? What are your FTP details?

You: "host: ftp.mysite.com, user: admin, pass: secret123"
AI:  [calls add_server → saves credentials]
     ✅ Server saved! Now deploying...
     [calls deploy_project → starts pipeline]
     🎉 Done! Site is live.

🔐 Environment Variables

| Variable | Required | Default | Description | |---|---|---|---| | OTOINSTALL_API_KEY | ✅ | — | Your OtoInstall API key | | OTOINSTALL_BASE_URL | ❌ | https://otoinstall.com | API base URL |

📦 What Happens During Deployment

OtoInstall runs an 8-stage pipeline automatically:

📦 Extract → 🔍 Security Scan → 🔎 Detect → 🧪 Compat Check
    → 🔧 Auto-Fix → 🏗️ Build → 🚀 Deploy → ✅ Verify

Auto-Fix includes:

• Creates .env from .env.example with real credentials
• Generates .htaccess for Apache URL rewriting
• Fixes file permissions (chmod)
• Creates install.php for database setup
• Adjusts absolute paths to relative
• PHP version compatibility fixes
• Node.js npm install && npm run build

📦 Local Development

git clone https://github.com/ovkdigital/otoinstall.git
cd packages/mcp-server
npm install
npm run build

Test with MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

License

MIT © OtoInstall