Your AI agent ships the site itself

Claude: web, Desktop and mobile

One custom connector covers claude.ai, the Desktop app, the mobile apps and Cowork.

1. Click Add to Claude, or open Customize > Connectors, click + Add and choose Add custom connector.
2. Name it VibeDeploy and enter the URL below (the Add to Claude button fills in both), then click Continue.
3. Keep the detected settings (if Claude asks for an OAuth client, choose Register automatically), click Add, and sign in to VibeDeploy when Claude asks.

https://mcp.vibedeploy.be/mcp

Claude's help center says the Free plan includes one custom connector. On Team and Enterprise plans an owner adds the connector for the organization, and each member then connects it with their own VibeDeploy sign-in.

Guide: put a Claude artifact online

Claude Code

Add the server once for your user account, and every project can use it.

1. Run the command below in a terminal.
2. Start Claude Code, run /mcp, pick vibedeploy and sign in in the browser.
3. To share the setup with a team, commit the .mcp.json file below to the project instead.

claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp

{
  "mcpServers": {
    "vibedeploy": {
      "type": "http",
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

Guide: deploy from Claude Code

ChatGPT

Two routes, depending on what your ChatGPT plan offers.

1. If your ChatGPT plan lets you add custom MCP servers, open Plugins in ChatGPT on the web, click + and choose Add custom MCP server. Some plans and workspaces need developer mode switched on first; OpenAI's help center describes that switch under Settings > Apps > Advanced settings.
2. Name it VibeDeploy, enter the URL below, choose OAuth, accept the risk warning and click Create as a plugin. Install the plugin, then sign in to VibeDeploy when asked.
3. Or paste the deploy guide from your VibeDeploy dashboard into any chat. ChatGPT then sends the files itself, or gives you a deploy page to open in your browser.

https://mcp.vibedeploy.be/mcp

Publishing needs write access. OpenAI's help center lists full MCP support, write actions included, for Business, Enterprise and Edu workspaces, and says Pro accounts can connect MCP servers with read and fetch permissions in developer mode. Menus differ by plan and workspace, so follow what your ChatGPT shows.

Guide: host a site made with ChatGPT

OpenAI Codex CLI

Codex adds remote servers from the command line or from its config file.

1. Add the server and sign in with the two commands below.
2. Or add the block to ~/.codex/config.toml. The longer tool timeout gives large uploads and builds time to finish.

codex mcp add vibedeploy --url https://mcp.vibedeploy.be/mcp
codex mcp login vibedeploy

[mcp_servers.vibedeploy]
url = "https://mcp.vibedeploy.be/mcp"
tool_timeout_sec = 600

Cursor

One click with the install link, or one entry in mcp.json.

1. Click Add to Cursor and confirm the install when Cursor asks.
2. Or add the entry below to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json for one project.
3. Sign in to VibeDeploy when Cursor asks, then ask Agent to deploy.

{
  "mcpServers": {
    "vibedeploy": {
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

Guide: deploy from Cursor

VS Code with GitHub Copilot

VS Code installs the server from a link or from a file in your workspace.

1. Click Install in VS Code and confirm in VS Code.
2. Or add the entry below to .vscode/mcp.json in your project.
3. Trust and start the server, sign in to VibeDeploy when VS Code asks, then ask Copilot in chat to deploy.

{
  "servers": {
    "vibedeploy": {
      "type": "http",
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

Guide: deploy from GitHub Copilot

Windsurf (now Devin Desktop)

Windsurf was renamed Devin Desktop on 2 June 2026, and new chats run on the Devin Local agent. Its MCP servers live in the Devin config file.

1. Add the first entry below to ~/.config/devin/mcp_config.json on macOS or Linux, or to %APPDATA%\devin\mcp_config.json on Windows.
2. Or let the Devin CLI write that entry with the command below.
3. On the first VibeDeploy tool call you are asked to sign in in the browser. If VibeDeploy later shows Needs auth in Devin Local's MCP list, click Authenticate next to it; with the Devin CLI, devin mcp logout vibedeploy followed by devin mcp login vibedeploy does the same.
4. Windsurf builds from before the rename run the Cascade agent, which reads ~/.codeium/windsurf/mcp_config.json and expects serverUrl instead of url.

{
  "mcpServers": {
    "vibedeploy": {
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

devin mcp add -s user vibedeploy https://mcp.vibedeploy.be/mcp

{
  "mcpServers": {
    "vibedeploy": {
      "serverUrl": "https://mcp.vibedeploy.be/mcp"
    }
  }
}

Guide: deploy from Windsurf

Gemini CLI

Gemini CLI keeps remote servers in ~/.gemini/settings.json under the key httpUrl.

1. Add the server for your user account with the command below.
2. Sign in from a Gemini CLI session with /mcp auth vibedeploy.

gemini mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp

Google moved unpaid and Google One users from Gemini CLI to Antigravity CLI on 18 June 2026. We have not tested Antigravity yet, so it is not covered here.

Any other MCP client

Every client that supports remote MCP servers with OAuth can connect.

1. Point the client at the Streamable HTTP endpoint. It discovers the OAuth server, registers itself and asks you to sign in.
2. Most clients use a url key. Windsurf builds from before Devin Desktop use serverUrl, Gemini CLI uses httpUrl, and VS Code wraps servers in a servers object with type http.
3. Clients that cannot sign in with OAuth can send a deploy token from your VibeDeploy dashboard as an Authorization: Bearer header.

{
  "mcpServers": {
    "vibedeploy": {
      "url": "https://mcp.vibedeploy.be/mcp"
    }
  }
}