Connect your AI assistant

Use Webtzm from Claude, ChatGPT, Cursor, Gemini CLI and many more, or any assistant that supports MCP: list your forms, put a form's code into the site it is building, create a form, and change its settings.

What it does

MCP (the Model Context Protocol) is the open standard assistants use to reach outside tools. Webtzm publishes one connector. Once an assistant is connected it can read your forms and, if you allow it, change them.

• List your forms with their status, Google output and recent activity.
• Put a form's code into the site the assistant is building, with your site's own styles applied to it.
• Create a form that delivers to a new Google Sheet.
• Change a form's name, fields, allowed sites, success message, anti-spam check, or owner alert.
• Pause a form, or resume it.

It works with Claude, ChatGPT, Grok, coding agents such as Cursor, VS Code, Zed and OpenCode, and every other client that supports remote MCP servers; the full list is below. That includes the clients people use to run open models such as Qwen, GLM, DeepSeek, Llama and Kimi: the model is whichever one you pick in the client, and the client makes the connection to Webtzm.

The connector URL

Every client takes the same address.

https://webtzm.com/mcp/workspace

Choose how to connect

Assistant keys

Many clients that run open models cannot complete a sign-in. They use a key instead.

1. 1
   Create the key

   Open Account > AI assistants in the workspace, give the key a label, and choose View only or View and make changes.

2. 2
   Copy it now

   The key is shown once, when you create it. Webtzm keeps no copy you can read back, so if it is lost, revoke it and create another.

3. 3
   Send it as a header

   Put it in the client's settings as Authorization: Bearer YOUR_WEBTZM_KEY. Where a client reads environment variables, keep the key in WEBTZM_KEY rather than in a file.

4. 4
   Revoke it when you are done

   The same page lists each key with when it was last used and a Revoke button. A revoked key stops working on its next request.

Set up your client

Find your client below. Every section uses the connector URL above.

Claude

Claude on the web and in Desktop takes remote connectors, so this is the shortest setup.

1. Open Customize > Connectors.
2. Select + Add, then Add custom connector.
3. Name it Webtzm, paste the connector URL, and select Continue.
4. Choose Sign in now and finish on the Webtzm page: pick the workspace and the access level.

For Team and Enterprise accounts, an owner adds the connector first under Organization settings > Connectors, and each member then selects Connect. Anthropic's steps are in Get started with custom connectors.

https://webtzm.com/mcp/workspace

ChatGPT

ChatGPT connects to remote servers from the web app, on a personal account including the Free plan. A Business or Enterprise workspace may not let members create custom connectors; use a personal account if yours refuses. Menu names change from release to release, so check OpenAI's developer mode guide if yours differ.

1. Turn on Developer mode under Settings > Security and login.
2. Open Plugins, select +, then Create custom MCP server and Create MCP App. Name it Webtzm.
3. Paste the connector URL and choose OAuth as the authentication.
4. Select Sign in with Webtzm and complete the sign-in on the Webtzm page: pick the workspace and the access level.
5. In a chat, choose + and select Webtzm, then ask for your forms.

https://webtzm.com/mcp/workspace

Grok

Grok takes remote connectors from the web app. xAI's documentation says to enter the server's address and complete any sign-in it asks for; it does not say which sign-in methods a custom connector supports, so if Grok cannot sign in to Webtzm, use another assistant from this list.

1. Open grok.com/connectors, select New Connector, then Custom.
2. Paste the connector URL.
3. Complete the sign-in on the Webtzm page: pick the workspace and the access level.

https://webtzm.com/mcp/workspace

Reference: Grok connectors.

Mistral Le Chat

Le Chat takes custom MCP connectors over Streamable HTTP. Adding one is an administrator task: on the Free, Pro and Student plans the account owner is the administrator.

1. Open Connectors, select + Add Connector, and open the Custom MCP Connector tab.
2. Give it a name with letters and numbers only, such as Webtzm, and paste the connector URL.
3. Select Connect, then sign in on the Webtzm page: pick the workspace and the access level.
4. To use a key instead, choose the token authentication option and paste your assistant key as the token. Le Chat sends it as an Authorization header.

Name:           Webtzm
Server URL:     https://webtzm.com/mcp/workspace
Authentication: OAuth 2.1   (or Token, with your assistant key)

Reference: Mistral MCP connectors.

Claude Code

1. Run the command below in your terminal.
2. Inside Claude Code, run /mcp, choose webtzm, and sign in in the browser.

claude mcp add --transport http webtzm https://webtzm.com/mcp/workspace

To use a key instead, add it as a header when you add the server.

export WEBTZM_KEY="YOUR_WEBTZM_KEY"
claude mcp add --transport http webtzm https://webtzm.com/mcp/workspace \
  --header "Authorization: Bearer $WEBTZM_KEY"

Reference: Claude Code MCP documentation.

Cursor

1. Open ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project.
2. Add the server below.
3. If your version of Cursor does not offer a sign-in for it, use the key version instead.

{
  "mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer ${env:WEBTZM_KEY}"
      }
    }
  }
}

Reference: Cursor MCP documentation.

VS Code

1. Run MCP: Add Server from the Command Palette, or create .vscode/mcp.json in your project.
2. Add the server below.
3. If VS Code does not offer a sign-in for it, use the key version. VS Code asks for the key once and stores it for you.

{
  "servers": {
    "webtzm": {
      "type": "http",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "servers": {
    "webtzm": {
      "type": "http",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer ${input:webtzm-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "webtzm-key",
      "description": "Webtzm assistant key",
      "password": true
    }
  ]
}

Reference: VS Code MCP configuration reference.

Google Antigravity

Antigravity is Google's agentic IDE. It takes remote servers by address and can sign in with OAuth.

1. Open the ... menu at the top of the agent panel, select MCP Servers, then Manage MCP Servers and View raw config.
2. Add the server below. Antigravity names the remote address serverUrl, not url.
3. Save, then sign in to Webtzm in the browser when Antigravity asks. For a key, use the second version.

{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

The Antigravity command line reads the same format from ~/.gemini/config/mcp_config.json, or from .agents/mcp_config.json for one project.

Reference: Antigravity MCP documentation.

Windsurf

1. In the Cascade panel, open the ... menu and select Open MCP config file.
2. Add the server below. Windsurf starts the sign-in when the server asks for one.
3. For a key, use the second version. Windsurf reads WEBTZM_KEY from your environment.

{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer ${env:WEBTZM_KEY}"
      }
    }
  }
}

Reference: Windsurf MCP documentation.

Zed

Zed keeps MCP servers under context_servers in its settings file, not mcpServers. A remote server needs only its address, and Zed starts the sign-in on its own when the server has no Authorization header.

1. Open the Command Palette and run zed: open settings file, or select Settings > AI > MCP Servers > Add Server > Add Remote Server.
2. Add the server below and save.
3. Sign in to Webtzm in the browser when Zed asks. For a key, use the second version.

{
  "context_servers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "context_servers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: Zed MCP documentation.

JetBrains AI Assistant

JetBrains' documentation shows a remote MCP server as a bare address and does not describe request headers or a sign-in for it. The mcp-remote bridge works either way, so this section uses it. It needs Node.js.

1. Open Settings > Tools > AI Assistant > Model Context Protocol (MCP) and select Add.
2. Paste the server below as JSON and save. With the first version the bridge opens your browser so you can sign in to Webtzm.
3. For a key, use the second version and put the key where the placeholder is.

{
  "mcpServers": {
    "webtzm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://webtzm.com/mcp/workspace"]
    }
  }
}

{
  "mcpServers": {
    "webtzm": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://webtzm.com/mcp/workspace",
        "--header",
        "Authorization:${WEBTZM_AUTH}"
      ],
      "env": {
        "WEBTZM_AUTH": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Junie, JetBrains' coding agent for the command line, takes a remote address directly. Add the server to ~/.junie/mcp/mcp.json, or to .junie/mcp/mcp.json for one project, then run /mcp in Junie and sign in in the browser. For a key, add an Authorization header to the same entry.

{
  "mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

Reference: JetBrains AI Assistant MCP documentation and Junie CLI MCP configuration.

Cline

Cline is a coding agent inside VS Code that works with hosted and local models. It takes a remote server in its MCP settings file. Connect it with a key.

1. Select the MCP Servers icon in the Cline panel, open the Configure tab, and select Configure MCP Servers.
2. Add the server below, with your key in place of the placeholder.
3. Save, and check that the server's tools are listed.

{
  "mcpServers": {
    "webtzm": {
      "type": "streamableHttp",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: Cline MCP documentation.

Roo Code

Roo Code is a coding agent inside VS Code that works with hosted and local models. It names the transport streamable-http, where Cline writes streamableHttp, so the two settings are not interchangeable. Connect it with a key.

1. Open Roo Code's MCP settings and select Edit Global MCP, or Edit Project MCP to keep the server in .roo/mcp.json for one project.
2. Add the server below, with your key in place of the placeholder.
3. Save, and check that the server's tools are listed.

{
  "mcpServers": {
    "webtzm": {
      "type": "streamable-http",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: Roo Code MCP documentation.

Kilo Code

Kilo Code is a coding agent for VS Code and the terminal that works with hosted and local models. It keeps remote servers under an mcp key in its kilo.jsonc file and starts a sign-in on its own when a server asks for one.

1. Open Settings > MCP and select Add Server, or edit ~/.config/kilo/kilo.jsonc for every project, or .kilo/kilo.jsonc for one project.
2. Add the server below.
3. Connect it and sign in to Webtzm in the browser. For a key, use the second version and set WEBTZM_KEY in the environment Kilo Code starts from.

{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer {env:WEBTZM_KEY}"
      },
      "oauth": false
    }
  }
}

Reference: Kilo Code MCP documentation.

Continue

Continue is an open-source assistant for VS Code and JetBrains. It reads MCP server files from .continue/mcpServers/ and sends the headers you give under requestOptions. Its documentation does not describe a sign-in for remote servers, so connect it with a key.

1. Create .continue/mcpServers/webtzm.yaml in your workspace.
2. Add the server below, with your key in place of the placeholder, and save.
3. Switch Continue to Agent mode. Continue uses MCP tools in no other mode.

name: Webtzm
version: 0.0.1
schema: v1
mcpServers:
  - name: Webtzm
    type: streamable-http
    url: https://webtzm.com/mcp/workspace
    requestOptions:
      headers:
        Authorization: Bearer YOUR_WEBTZM_KEY

Reference: Continue MCP documentation.

Devin

This is Devin on the web. Adding a custom MCP server needs the Manage MCP Servers permission; without it, use Suggest MCP Integration to ask an administrator.

1. Open Customize > MCPs, select Add MCP, then Add custom MCP.
2. Name it Webtzm and choose the HTTP transport.
3. Paste the connector URL. Set authentication to OAuth to sign in, or to Auth Header to use a key.
4. Select Save, sign in to Webtzm if asked, and select Test tools to check the connection.

Transport:      HTTP
Server URL:     https://webtzm.com/mcp/workspace
Authentication: OAuth   (or Auth Header: Authorization = Bearer YOUR_WEBTZM_KEY)

Reference: Devin MCP servers and marketplace.

Amp

Amp is a coding agent for the terminal and editors. It signs in on its own to a remote server that supports it, and takes headers for one that does not. Sourcegraph Cody runs only local MCP servers, so it cannot take the connector URL directly; Amp is the assistant Sourcegraph points individual developers to.

1. Run the command below, or add the server under amp.mcpServers in ~/.config/amp/settings.json (.amp/settings.json for one project).
2. Start Amp. It opens the Webtzm sign-in in your browser.
3. For a key, use the settings version and set WEBTZM_KEY in the environment Amp starts from.

amp mcp add webtzm https://webtzm.com/mcp/workspace

{
  "amp.mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "amp.mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer ${WEBTZM_KEY}"
      }
    }
  }
}

Reference: Amp MCP documentation.

Gemini CLI

1. Add the server with the command below.
2. Start gemini and run /mcp auth webtzm to sign in in the browser.

gemini mcp add --transport http webtzm https://webtzm.com/mcp/workspace

To use a key, pass it as a header.

export WEBTZM_KEY="YOUR_WEBTZM_KEY"
gemini mcp add --transport http --header "Authorization: Bearer $WEBTZM_KEY" webtzm https://webtzm.com/mcp/workspace

Reference: Gemini CLI MCP server documentation.

Qwen Code

Qwen Code is a command-line coding agent that runs Qwen models. Connect it with a key.

export WEBTZM_KEY="YOUR_WEBTZM_KEY"
qwen mcp add --transport http webtzm https://webtzm.com/mcp/workspace \
  --header "Authorization: Bearer $WEBTZM_KEY"

Or add it to settings.json yourself. Qwen Code names the remote address httpUrl.

{
  "mcpServers": {
    "webtzm": {
      "httpUrl": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: Qwen Code MCP documentation.

OpenCode

OpenCode is an open-source terminal coding agent that works with hosted and local models. It keeps remote servers under an mcp key in opencode.json.

1. Add the server below to your opencode.json.
2. Run opencode mcp auth webtzm to sign in to Webtzm in the browser. OpenCode also starts the sign-in on its own when the server asks for one.
3. For a key, use the second version and set WEBTZM_KEY in the environment OpenCode starts from. oauth is turned off so OpenCode sends the key instead of starting a sign-in.

{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}

{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer {env:WEBTZM_KEY}"
      },
      "oauth": false
    }
  }
}

Reference: OpenCode MCP server documentation.

Goose

Goose is an open-source agent that works with hosted and local models. It registers a remote server as an extension.

1. Desktop: open the sidebar, select Extensions, then Add custom extension, and enter the connector URL.
2. Terminal: run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP).
3. For the key, or if Goose does not start a sign-in, follow Any other MCP client.

extensions:
  webtzm:
    name: Webtzm
    type: streamable_http
    uri: https://webtzm.com/mcp/workspace
    enabled: true
    timeout: 300

Reference: Goose extensions documentation.

Aider

Aider has no built-in MCP support at the time of writing: its documentation does not mention MCP, and native support is still an open request. There is nothing to configure, so Webtzm gives no Aider settings. Use an assistant from this list that supports MCP to read a form and put its code in your site, then continue in Aider with the code the assistant produced.

Open WebUI

Open WebUI runs local or hosted open models in a browser. It needs version 0.6.31 or later, and an administrator adds the connection.

1. Open Settings > Admin > Integrations and find External Tool Servers.
2. Select + Add Connection.
3. Set the type to MCP (Streamable HTTP) and paste the connector URL.
4. Choose OAuth 2.1 to sign in, or Bearer and paste an assistant key in the key field.
5. Save.

Type: MCP (Streamable HTTP)
URL:  https://webtzm.com/mcp/workspace
Auth: OAuth 2.1   (or Bearer, with your assistant key)

Reference: Open WebUI MCP documentation.

LM Studio

LM Studio runs open models on your own machine. Connect it with a key.

1. Open the Program tab in the right sidebar.
2. Select Install > Edit mcp.json.
3. Add the server below, with your key in place of the placeholder.

{
  "mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: LM Studio MCP documentation.

Cherry Studio

Cherry Studio is a desktop chat client for hosted and local models. It adds remote servers by address, with request headers for authorization.

1. Open Settings > MCP > MCP Servers and select Add.
2. Choose the streamable HTTP type and enter the connector URL.
3. Add the request header described under Any other MCP client, with your assistant key.
4. Save and enable the server, then check that its tools are listed.

URL:             https://webtzm.com/mcp/workspace
Request headers: Authorization: Bearer YOUR_WEBTZM_KEY

Reference: Cherry Studio MCP documentation.

LibreChat

LibreChat is a self-hosted chat interface for hosted and local models. Declare the server in librechat.yaml and let each person paste their own key, so one workspace is not shared across everyone on the instance.

mcpServers:
  webtzm:
    type: streamable-http
    url: https://webtzm.com/mcp/workspace
    headers:
      Authorization: "Bearer {{WEBTZM_KEY}}"
    customUserVars:
      WEBTZM_KEY:
        title: "Webtzm assistant key"
        description: "Create one in Webtzm under Account > AI assistants."
        sensitive: true

Reference: LibreChat MCP server settings.

AnythingLLM

AnythingLLM runs open and hosted models in a desktop app or in Docker. Its documentation describes remote servers with a streamable type and optional headers, and no sign-in for them, so connect it with a key.

1. Open the Agent Skills page and find its MCP servers section, or edit plugins/anythingllm_mcp_servers.json in your AnythingLLM storage folder.
2. Add the server below, with your key in place of the placeholder. The type is streamable, not streamable-http.
3. Save, and check that the server is running and lists its tools.

{
  "mcpServers": {
    "webtzm": {
      "type": "streamable",
      "url": "https://webtzm.com/mcp/workspace",
      "headers": {
        "Authorization": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: MCP in AnythingLLM.

Any other MCP client

A client that supports remote MCP servers needs three things. Where it asks for a transport, choose Streamable HTTP.

A client that supports MCP sign-in finds the rest from the URL and opens the Webtzm page. A client without sign-in sends the key header on every request. Webtzm answers in plain JSON, so older clients work too.

Transport: Streamable HTTP
URL:       https://webtzm.com/mcp/workspace
Header:    Authorization: Bearer YOUR_WEBTZM_KEY   (only when not signing in)

Local-only (stdio) clients

Some clients can only start a program on your machine. The mcp-remote bridge is that program: it speaks to the client locally and to Webtzm over the network. It needs Node.js.

{
  "mcpServers": {
    "webtzm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://webtzm.com/mcp/workspace"]
    }
  }
}

With a key, put the whole header value in an environment variable. Spaces inside a command argument are mangled on some systems, and the bridge's own documentation recommends this form.

{
  "mcpServers": {
    "webtzm": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://webtzm.com/mcp/workspace",
        "--header",
        "Authorization:${WEBTZM_AUTH}"
      ],
      "env": {
        "WEBTZM_AUTH": "Bearer YOUR_WEBTZM_KEY"
      }
    }
  }
}

Reference: mcp-remote.

What the assistant can do

These are the tools a connected assistant gets. The first group needs only View only; the second needs View and make changes.

Changes go through the same checks as the console: the same plan limits, allowed-site rules, and Google requirements. A refused change comes back as a plain sentence the assistant can act on.

What it cannot do

• Delete or archive a form. That stays in the console.
• Change billing or plans.
• Connect or disconnect Google.
• Create, read, or change keys and secrets, including Record Fetch keys and webhook secrets.
• Read what visitors submitted. It sees delivery status, not the contents of a submission.

Example prompts

• “List my Webtzm forms and tell me which ones received a submission recently.”
• “Add my Webtzm contact form to this page and match the site's styles.”
• “Create a Webtzm form called Workshop sign-up with name, email and message fields, allowed on https://www.example.com, and give me the code.”
• “Add https://staging.example.com to the allowed sites on my contact form.”
• “Pause the newsletter form until I say otherwise.”

Troubleshooting