Hatch

What the Hatch MCP server does

Hatch provides hosting for AI agents that need to publish a live website. Its defining operation is website publication through one tool call, giving an agent a direct way to make a site live rather than requiring a separate, manually performed hosting step.

The available description presents two hosting lifetimes: ephemeral and permanent. Ephemeral hosting is suitable when the published site only needs to exist temporarily. Permanent, or “forever,” hosting is intended for sites that should remain available after the initial agent interaction. The material does not specify how long ephemeral sites remain available or what conditions apply to permanent hosting.

How it works

An AI agent invokes Hatch through a single tool call to publish a live website. The agent-facing workflow is therefore centered on publication, while Hatch supplies the hosting destination for the resulting site. The source description does not identify the request schema, returned values, URL format, authentication flow, or the implementation used to host the site.

The hosting duration is part of the stated behavior: an agent can publish something temporary or choose an option intended to persist indefinitely. The available information does not explain whether an existing site can be updated, whether multiple sites can be managed, or whether a published site can be removed.

Tools and capabilities

The supported capability described for the Hatch MCP server is:

• Publishing a live website in one tool call.
• Hosting an agent-published site temporarily.
• Hosting an agent-published site indefinitely.

No additional tool names or operations are provided. In particular, the available material does not establish support for domain management, file operations, site updates, deployment logs, analytics, databases, or other hosting controls.

Limitations and notes

The repository is identified as the source, but no README content is available in the supplied material. As a result, installation commands, client configuration, environment variables, authentication requirements, supported input formats, and deployment details cannot be confirmed here.

The Hatch MCP server should be evaluated primarily for the narrow requirement described: allowing an AI agent to publish a live website through one call, with either temporary or indefinite hosting. Client compatibility is not documented in the available information, so a developer should verify support for the intended MCP client before adoption.

The description also does not define what “forever” means operationally, whether usage limits apply, or how ephemeral and persistent hosting are selected. Those details require documentation from the project before they can be relied on in production workflows.