Xhostd MCP server
{
"mcpServers": {
"xhostd": {
"type": "http",
"url": "https://mcp.xhostd.com/mcp/"
}
}
}{
"mcpServers": {
"xhostd": {
"type": "http",
"url": "https://mcp.xhostd.com/mcp/"
}
}
}{
"mcpServers": {
"xhostd": {
"type": "http",
"url": "https://mcp.xhostd.com/mcp/"
}
}
}{
"servers": {
"xhostd": {
"type": "http",
"url": "https://mcp.xhostd.com/mcp/"
}
}
}{
"mcpServers": {
"xhostd": {
"type": "http",
"url": "https://mcp.xhostd.com/mcp/"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.4.0
What it does
MCP server for xhostd, a hosting platform that deploys applications from code. Users push code, trigger deploys, and receive HTTPS URLs. Supports static sites, Node.js, Python, Docker, and background workers. Authentication uses browser-based Google OAuth through the MCP connection.
- Deploy a website or API to a live HTTPS URL by committing code and running the xhost skill.
- Create preview URLs for branches to test changes before merging to production.
- Check deployment status, view app metadata, inspect runtime logs, and manage channels and domains.
Tools this server exposes
| Tool | Does |
|---|---|
| xhost | Handles account setup, app creation, code deployment, preview channel management, and status inspection for applications on xhostd. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.