MCP Setup

Install Hatch on your AI tool

Hatch is Vibe Rooster's MCP connector — it lets your AI assistant publish a live website at https://your-name.theroost.dev in one tool call. No API key, no sign-in, no cloud account.

Server URL

https://mcp.theroost.dev/mcp
Jump to your tool

Claude.ai & Claude Desktop

Recommended. Claude connects directly over Streamable HTTP — no local install.

Claude.ai (web)

  1. Open Settings → Connectors.
  2. Click Add custom connector.
  3. Paste https://mcp.theroost.dev/mcp and set authentication to None.
  4. Save. Start a new chat and enable the Hatch connector for that conversation.

Custom connectors require Claude Pro, Max, Team, or Enterprise.

Claude Desktop (macOS, Windows, Linux)

Use the same Settings → Connectors → Add custom connector flow as Claude.ai. Fully quit and reopen Claude Desktop after adding — a window reload is not enough.

If your plan does not support custom connectors, use the mcp-remote bridge (requires Node 20+ on your PATH). Edit your Claude Desktop config:

OSConfig file
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hatch": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.theroost.dev/mcp", "--transport", "http-only"]
    }
  }
}

Quit and relaunch Claude Desktop after saving.

Claude Code

From any terminal (macOS, Windows, Linux):

claude mcp add --transport http hatch https://mcp.theroost.dev/mcp

Or add to a project-scoped .mcp.json in your repo root:

{
  "mcpServers": {
    "hatch": {
      "type": "http",
      "url": "https://mcp.theroost.dev/mcp"
    }
  }
}

Cursor

Cursor supports remote MCP over Streamable HTTP. Add Hatch globally or per project.

Option A — Settings UI

  1. Open Cursor Settings → Tools & MCP.
  2. Click New MCP Server (or edit the JSON directly).
  3. Add the Hatch entry below and reload Cursor.

Option B — Config file

ScopePath
Global (all projects)~/.cursor/mcp.json on macOS/Linux · %USERPROFILE%\.cursor\mcp.json on Windows
Project only.cursor/mcp.json in your project root
{
  "mcpServers": {
    "hatch": {
      "url": "https://mcp.theroost.dev/mcp"
    }
  }
}

No headers or auth token needed. Restart Cursor or reload the window after saving.

Windsurf

  1. Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows).
  2. Run Windsurf: Configure MCP Servers (or click the hammer icon in Cascade → Configure).
  3. Add Hatch to ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json).
Windsurf uses serverUrl for remote servers — not url. Copying a Cursor config without changing the field name will silently fail.
{
  "mcpServers": {
    "hatch": {
      "serverUrl": "https://mcp.theroost.dev/mcp"
    }
  }
}

Click Refresh in the Cascade MCP toolbar after saving.

Other MCP clients

Any client that speaks local stdio but not remote HTTP can bridge with mcp-remote (Node 20+). Merge this into your client's MCP config file:

{
  "mcpServers": {
    "hatch": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.theroost.dev/mcp", "--transport", "http-only"]
    }
  }
}

Works with VS Code extensions, Cline, Zed (via external MCP), and other stdio-based setups. Clients that support Streamable HTTP natively should use the URL directly instead.

Try it — example prompts

Once Hatch shows as connected (you should see tools like hatch, upload, and lookup), paste any of these into your assistant:

“Hatch me a one-page landing site for my coffee shop and give me the live link.” → creates a new site instantly
“Here's my portfolio — index.html, styles.css, and three photos. Put it online.” → uploads your files to a live URL
“Add a contact page to the site you just made.” → adds a file to the existing site
“What was the URL of the site named ‘tacobot’?” → looks up a previous site by slug
“Build a status dashboard from this script and tell me how to keep it updating.” → live URL now; refresh stays on your cron, CI, or re-ask
Free sites last 48 hours. Sites created through Hatch are temporary demos — perfect for trying the connector. To keep a site permanently, publish first, then upgrade your account.

More help