Hostsmith
@hostsmith
Deploy static sites on Hostsmith - give it a file, get a live HTTPS URL. EU/US residency.
Overview
What is Hostsmith?
Hostsmith is an official Model Context Protocol (MCP) server for the Hostsmith hosting platform. It enables agents to deploy file contents to a publicly accessible HTTPS URL within seconds, without requiring a repository or build step. It is designed for developers building agentic workflows that need instant static hosting.
How to use Hostsmith?
Configure the server in your MCP client using either a remote URL (https://mcp.hostsmith.net/mcp) or by running the stdio command npx -y @hostsmith/mcp-server. Authentication occurs via OAuth 2.0—no static tokens are supported. The first tool call triggers a browser-based OAuth flow to authorize the connection against your Hostsmith account. Environment variables such as HOSTSMITH_URL, HOSTSMITH_API_DOMAIN, and PORT can be used to customize the server.
Key features of Hostsmith
- Deploy files to a live URL in seconds
- No repository or build configuration required
- Supports custom domains and private sites
- Choose EU or US data residency
- MCP-native with OAuth 2.0 authentication
- Provides tools for site and domain management
Use cases of Hostsmith
- Claude Code shipping an HTML report as a live URL
- Cursor previewing a generated demo instantly
- Claude Desktop publishing a one-pager
- Uploading large binary files via direct-to-S3 upload
- Deploying static sites without a CI pipeline
FAQ from Hostsmith
How does Hostsmith authenticate?
Authentication uses OAuth 2.0 exclusively. Static access tokens are not supported. The server triggers a browser-based OAuth flow on the first tool call.
Where does my data reside?
You can choose EU or US data residency. The partition argument in tool calls lets you control the region; if omitted, the partition is inferred from your access token.
What transport does Hostsmith use?
It supports Streamable HTTP (remote URL) and stdio (local command). The remote URL is https://mcp.hostsmith.net/mcp and the stdio command is npx -y @hostsmith/mcp-server.
What should I do if I get a 401 error?
A 401 response means the OAuth session has expired. Reconnect from your MCP client to re-authorize.
Can I customize the API endpoint?
Yes. Use the HOSTSMITH_API_DOMAIN environment variable to override the upstream API domain, or HOSTSMITH_BASE_URL to set a single fixed API base URL.