Install Hatch on your AI tool

Hatch is Vibe Rooster's MCP connector — one public URL, the same tools, whichever agent you use. No API key, no sign-in, no cloud account. If the client can add a remote Streamable HTTP server, it can Hatch.

https://mcp.theroost.dev/mcp

We label what we know. Tested means we have hatched a live site from that client. Expected means the client speaks the same transport Hatch already serves. New means we have not run a dedicated pass yet.

Claude.ai & Claude Desktop Tested

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:

{
  "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 Tested

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 Tested

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

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

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

Grok Tested

Grok Bot on the web uses custom MCP connectors. Hatch is a public HTTPS endpoint, so no tunnel is required.

1. Open grok.com/connectors.
2. Click New Connector, then Custom.
3. Enter https://mcp.theroost.dev/mcp. Leave authentication empty.
4. Save. Grok discovers Hatch's tools and makes them available in chat.

From the Grok CLI:

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

Or declare it in ~/.grok/config.toml:

[mcp_servers.hatch]
url = "https://mcp.theroost.dev/mcp"

Hermes Tested

Hermes Agent talks to remote HTTP MCP servers from ~/.hermes/config.yaml. Hatch needs no OAuth and no bearer token.

mcp_servers:
  hatch:
    url: "https://mcp.theroost.dev/mcp"

Start a new Hermes session (or /reload-mcp) so it discovers hatch, upload, and lookup. You can also ask Hermes to add that URL as a custom MCP server — it writes the same config.

OpenClaw Tested

1. Open the Control UI and go to Settings → MCP.
2. Under Configured servers, select Add server.
3. Name it hatch and pick transport Streamable HTTP.
4. Enter https://mcp.theroost.dev/mcp and add the server.

Or write it into OpenClaw config:

{
  mcp: {
    servers: {
      hatch: {
        url: "https://mcp.theroost.dev/mcp",
        transport: "streamable-http",
        enabled: true,
      },
    },
  },
}

Probe with openclaw mcp probe hatch if you want a live capabilities check.

Codex / OpenAI Expected

OpenAI Codex CLI supports remote Streamable HTTP MCP. We have not run Hatch on Codex yet. The transport matches what Hatch already serves, so we expect it to work.

codex mcp add hatch --url https://mcp.theroost.dev/mcp

Or add to ~/.codex/config.toml:

[mcp_servers.hatch]
url = "https://mcp.theroost.dev/mcp"

Hatch is unauthenticated — skip codex mcp login. Confirm with /mcp in a Codex session. If a tool list does not appear, tell us at hello@viberooster.com.

Muse New

Muse is Cursor's new model, not a separate MCP client. If Hatch is already in Cursor's mcp.json, Muse uses the same connector.

We think it will work. We have not run a dedicated Muse pass yet. Add Hatch the Cursor way, then ask Muse to hatch.

Windsurf Expected

Windsurf speaks remote MCP. We have not run a Hatch pass on 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).

{
  "mcpServers": {
    "hatch": {
      "serverUrl": "https://mcp.theroost.dev/mcp"
    }
  }
}

Click Refresh in the Cascade MCP toolbar after saving.

Other MCP clients

If the client has a field for a remote MCP URL, paste https://mcp.theroost.dev/mcp and leave auth empty. That is the whole integration.

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:

More help

• Connect Hatch — what the URL is, who we have tested, tools, tiers, and limits
• Privacy Policy — what Hatch stores and for how long
• hello@viberooster.com — questions and feedback, including “it worked on my agent”