surge

This MCP server provides a Surge.sh toolkit that lets AI models authenticate with Surge and deploy projects to Surge.sh with a randomized subdomain. Once running, you can use the server to log in to a Surge account and push deployments for hosting. The tooling exposed through MCP aligns with Surge’s standard workflow: first authenticate, then deploy, receiving a ready-to-use domain for your hosted project. Use the built-in commands to manage sessions and trigger deployments through the MCP API, enabling automated hosting workflows for model-driven assets.

Prerequisites:

• Node.js and npm should be installed on your system.
• Internet access to fetch the MCP server via npx.

Installation steps:

1. Install Node.js and npm if not already installed. You can download from https://nodejs.org/ and follow the installation instructions for your OS.
2. Run the MCP server installation command: npx -y https://github.com/xhyqaq/surge-mcp-server
3. After installation completes, start the MCP server using your preferred MCP runner (the specific start command may be provided by the installation output). Ensure the server is reachable by your MCP client.
4. If needed, configure environment variables for Surge authentication or deployment settings as described in your deployment environment documentation.

Notes and tips:

• The server uses a one-shot npx installation approach, so your environment must allow network access to download the MCP server package.
• Surge authentication often requires a login via Surge CLI; ensure you have valid Surge.io credentials configured on the running runner.
• Deployment will generate a random subdomain, which is suitable for ephemeral testing but may not be ideal for production links.
• If you encounter authentication or deployment failures, verify that your Surge session is valid and that the MCP host can reach Surge’s services.
• Since the server is accessed via npx URL, there is no separate npm package name to reference in npm-based workflows.