sitelauncher-mcp-server
LocalAbout sitelauncher-mcp-server
sitelauncher-mcp-server lets AI agents deploy HTTPS websites through SiteLauncher, using instant subdomains or custom .xyz domains. Deployment is payment-gated with USDC on Base.
Key features
- 01Deploy HTTPS sites to instant subdomains
- 02Register and configure custom .xyz domains
- 03Use degen and agent templates
- 04Check domain availability and deployment status
- 05List wallet-owned sites and domain options
Use cases
- 01Publish a quick website on a SiteLauncher subdomain
- 02Deploy a site with a registered .xyz domain
- 03Check progress on a custom-domain deployment
MCP support
It exposes deployment, domain lookup, status, and site-listing tools to MCP clients. It supports stdio and Streamable HTTP transports.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y sitelauncher-mcp-serverSITELAUNCHER_API_URLSiteLauncher API base URLLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMESiteLauncher MCP Server
MCP server for deploying live HTTPS websites in seconds via SiteLauncher.
- Instant subdomains ($1 USDC) - deploy to
yourname.sitelauncher.xyzwith SSL - Custom .xyz domains ($10 USDC) - register, DNS, SSL, deploy automatically
- Templates - degen (memecoin) and agent (AI agent profile) styles
- Payments - USDC on Base chain
Tools
| Tool | Description |
|---|---|
deploy_site | Deploy a website (requires USDC payment tx hash) |
check_availability | Check if a custom .xyz domain is available |
check_status | Poll order progress for custom domain deploys |
list_sites | List all sites owned by a wallet address |
list_domains | List available parent domains for subdomains |
domain_capacity | Check daily domain registration capacity |
health | Check service health and dry_run status |
Installation
Claude Desktop / Claude Code (stdio)
Add to your MCP settings:
{
"mcpServers": {
"sitelauncher": {
"command": "npx",
"args": ["-y", "sitelauncher-mcp-server", "--stdio"]
}
}
}
Streamable HTTP
npx sitelauncher-mcp-server
Starts an HTTP server on port 3100 (override with MCP_PORT env var). MCP endpoint: http://localhost:3100/mcp
Environment Variables
| Variable | Default | Description |
|---|---|---|
SITELAUNCHER_API_URL | https://sitelauncher.xyz/api | API base URL |
MCP_PORT | 3100 | HTTP server port (non-stdio mode) |
How It Works
- An AI agent sends USDC on Base chain to the SiteLauncher wallet
- The agent calls
deploy_sitewith the transaction hash and site details - SiteLauncher verifies payment on-chain, generates the site, and deploys it
- The agent receives the live URL
For custom domains ($10 USDC), the pipeline registers the domain via Porkbun, sets up DNS, provisions SSL via Let's Encrypt, and deploys. Use check_status to poll progress.
Payment
All payments are USDC on Base chain. Send to the SiteLauncher receive wallet before calling deploy_site.
| Service | Price |
|---|---|
| Instant subdomain | $1 USDC |
| Custom .xyz domain | $10 USDC |
| Domain renewal | $16 USDC |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.