Before You Start #
You can connect WebOps to an AI tool that supports MCP (Model Context Protocol). A single connection is linked to your WebOps account, so the AI tool can work with the websites available on your account. Before starting, make sure you can sign in to your WebOps account.
Choose Your AI Tool #
WebOps provides connection instructions for the following AI tools and development environments:
- Claude.ai (Web)
- Claude Desktop (Mac / Windows)
- Claude Code (CLI)
- ChatGPT (Web)
- Codex CLI (CLI & IDE extension)
- Antigravity (Code editor)
- Antigravity CLI (CLI)
- Cursor (Code editor)
- Devin Desktop (formerly Windsurf)
- Zed (Code editor)
- Qwen Code (CLI)
- Kimi Code CLI (CLI)
- Zencoder (JetBrains plugin)
Claude (Web, Desktop and Code) is the AI tool WebOps has verified. The other tools follow the general MCP steps, and their menus and wording may differ.
Your WebOps MCP Connection Details #
When adding WebOps to your AI tool, you will need your WebOps MCP connection URL.
Connector name (Claude): WebOps
Server name (everywhere else): webops
MCP URL: Use the WebOps MCP URL shown in your MCP settings in WebOps.
In the steps below, <URL> means your WebOps MCP URL. Your connection provides access to the websites available on your WebOps account, so you do not need a separate connection for each website.
1. Claude.ai (Web) #
- Open Claude — go to claude.ai and sign in to your account.
- Go to Connectors — open Customize, then Connectors, and click +.
- Add custom connector — click “Add custom connector”, then enter a name and the WebOps MCP URL. Name to enter: WebOps. This is the name you will see in Claude afterwards.
- Sign in and approve — a browser window opens; sign in to WebOps and approve.
Note: on the Free plan you can add one custom connector. On Team and Enterprise, an Owner adds it for the organization, then members connect to it.
2. Claude Desktop (Mac / Windows) #
Same as Claude.ai (Web), except the first step is to open the Claude desktop app and sign in.
Note: the same plan limits apply. In some versions of the app, Connectors is under Settings instead.
3. Claude Code (CLI) #
- Add the connector:
claude mcp add --transport http webops <URL>
- Sign in — run
/mcpin Claude Code, choosewebops, and sign in. A browser window opens to approve.
4. ChatGPT (Web) #
- Enable Developer mode — in ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode.
- Add the plugin — open Settings, then Plugins, click Add, enter a name and paste your WebOps MCP URL, then set the authentication mode to OAuth.
- Create and authorize — click Create; an authorization popup opens. Sign in to WebOps and approve.
Note: Developer mode is a beta feature, available on paid plans including Go, Plus, Pro, Business, Enterprise and Edu, not Free. On Business, Enterprise and Edu it is under Settings, then Apps, then Advanced settings.
Note: set the plugin up on the web. Once added, it becomes available in the ChatGPT desktop and mobile apps; update or restart them if needed.
5. Codex CLI (CLI & IDE extension) #
- Add the server:
codex mcp add webops --url <URL>
- Sign in:
codex mcp login webops, then approve in the browser.
Note: the Codex IDE extension uses the same setup.
6. Antigravity (Code editor) #
- Open the MCP configuration — open Settings, then Customizations, scroll to Installed MCP Servers, and click Open MCP Config. This opens
~/.gemini/config/mcp_config.json. - Add the server and save:
{ "mcpServers": { "webops": { "serverUrl": "<URL>" } } } - Sign in and approve when Antigravity prompts you.
7. Antigravity CLI (CLI) #
- Open
~/.gemini/config/mcp_config.json, and create it if it does not exist. - Add the same
serverUrlconfiguration as Antigravity and save. Antigravity CLI usesserverUrl, noturl. - Reload and sign in — run
/mcpin Antigravity CLI to reload, then approve in the browser.
8. Cursor (Code editor) #
- Open
~/.cursor/mcp.json, and create it if it does not exist. - Add and save:
{ "mcpServers": { "webops": { "url": "<URL>" } } } - Sign in and approve when Cursor prompts you.
9. Devin Desktop (formerly Windsurf) #
- Open
%APPDATA%\devin\mcp_config.json(that isC:\Users\<name>\AppData\Roaming\devin\mcp_config.json), and create it if it does not exist. Devin Desktop usesserverUrl, noturl. If you have an older config at~/.codeium/windsurf/mcp_config.json, Devin offers to migrate it when it launches. - Add and save:
{ "mcpServers": { "webops": { "serverUrl": "<URL>" } } } - Restart and sign in — sign-in opens in your browser the first time the server is used. If
webopsshows “Needs auth” in Open customizations, click “Authenticate”, then approve.
Note: with the Devin CLI you can instead run devin mcp add -s user webops <URL>, then devin mcp login webops.
10. Zed (Code editor) #
- Open MCP settings — Settings, then AI, MCP Servers, Add Server, Add Remote Server.
- Add the server — enter the name webops and the URL. Do not add an Authorization header.
- Click “Authenticate”, then sign in and approve.
Note: requires Zed 0.230 or later.
11. Qwen Code (CLI) #
- Add the server:
qwen mcp add --transport http webops <URL>
- Sign in — run
/mcp, selectwebops, choose Auth, then approve in the browser.
12. Kimi Code CLI (CLI) #
- Add the server:
kimi mcp add --transport http --auth oauth webops <URL>
This writes the server to
~/.kimi/mcp.jsonautomatically. - Sign in:
kimi mcp auth webops, then approve in the browser.
Note: run kimi mcp test webops to verify the connection, or kimi mcp list to see your servers.
13. Zencoder (JetBrains plugin) #
- Open Agent Tools — in your JetBrains IDE, open the Zencoder panel, click ⋮, then Agent Tools, Add custom MCP.
- Add the server — enter the name webops, paste the configuration, then Install:
{ "url": "<URL>", "auth": "oauth2" } - Sign in and approve when Zencoder prompts you.
Note: these steps are for JetBrains IDEs. Zencoder is still rolling out support for this connection type in VS Code.