Enter app

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.

Before you start

Sign in to Webtzm with Google and open the workspace you want the assistant to use. Connecting needs nothing else: no install, no code.

Connected or not

An assistant can create or change your forms only once it is connected, with Google sign-in or an access key. Connect once, then just ask in your own words. Use with your AI assistant, in the console's top bar, lists the assistants you can connect and how; with no connection selected, the panel's Setup shows Your AI assistant with Things you can ask, such as a contact form, a form where each person can edit or remove their own entry, or what is failing, and none of them needs a form picked first. The Webtzm helper answers “connect to Claude”, “create a key” and “show my keys” too.

Without a connection, an assistant can still write the HTML. Get the form code, under Advanced in a connection's Setup, has Copy prompt for AI: the form's code, its allowed sites, and the rules that keep it working — keep every name attribute, the hidden _webtzm_form input, the form's action and data-webtzm-form, and the script tags, and restyle freely. Paste it into any chat. It holds no key or other secret.

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.
  • With Pro, make a whole set in one request: the form, the forms that let each person change or remove their own entry from a link in their row, and Record Fetch so your site or app can read the rows. It can also add those to a form you already have, or turn the links on and off.

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.

Connector URL
https://webtzm.com/mcp/workspace

Choose how to connect

Preferred Sign in

The client opens a Webtzm page. Pick the workspace the assistant may use and one of two levels: View and make changes, chosen for you, or View only. If the workspace has not connected Google yet, the same page offers Connect Google next, ticked: every form sends its submissions to a Google Sheet in your Drive, so the assistant needs it to create forms. Nothing is pasted anywhere, and you can disconnect at any time.

When a client cannot sign in Assistant key

A key you create in the console and paste into the client's settings, sent as an Authorization: Bearer header. It carries the same workspace and access level a sign-in would, and you can revoke it at any time. How keys work.

Assistant keys

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

  1. Create the key

    With no connection selected, open the panel's Setup. Under Your AI assistant, in Access keys, give the key a name, choose View only or View and make changes, and select Create key. Asking the Webtzm helper to “create a key” opens the same place.

  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. 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. Revoke it when you are done

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

Treat a key like a password

Anyone holding it can do what its access level allows in that workspace. Keep it out of files you commit or share, and use a View only key unless the assistant needs to make changes. Assistants cannot create keys; they can only be created in the console.

Set up your client

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

ClientConnects with
Claude (claude.ai and Desktop)Sign in
ChatGPTSign in
GrokSign in
Mistral Le ChatSign in or key
Claude CodeSign in or key
CursorSign in or key
VS CodeSign in or key
Google AntigravitySign in or key
WindsurfSign in or key
ZedSign in or key
JetBrains AI AssistantSign in or key, through a bridge
ClineKey
Roo CodeKey
Kilo CodeSign in or key
ContinueKey
DevinSign in or key
AmpSign in or key
Gemini CLISign in or key
Qwen CodeKey
OpenCodeSign in or key
GooseSee the section
AiderNot supported yet
Open WebUISign in or key
LM StudioKey
Cherry StudioKey
LibreChatKey
AnythingLLMKey
Any other MCP clientSign in or key
Clients that only run local serversSign in or key

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.

Connector URL
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 guide to connecting a custom MCP server 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.
Connector URL
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.
Connector URL
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.
Le Chat connector
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 Code, sign in
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.

Claude Code, assistant key
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.
mcp.json
{
  "mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
mcp.json with an assistant key
{
  "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.
mcp.json
{
  "servers": {
    "webtzm": {
      "type": "http",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
mcp.json with an assistant key
{
  "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.
mcp_config.json
{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace"
    }
  }
}
mcp_config.json with an assistant key
{
  "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.
mcp_config.json
{
  "mcpServers": {
    "webtzm": {
      "serverUrl": "https://webtzm.com/mcp/workspace"
    }
  }
}
mcp_config.json with an assistant key
{
  "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.
settings.json
{
  "context_servers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
settings.json with an assistant key
{
  "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.
MCP server JSON
{
  "mcpServers": {
    "webtzm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://webtzm.com/mcp/workspace"]
    }
  }
}
MCP server JSON with an assistant key
{
  "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.

mcp.json for Junie
{
  "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.
Cline settings
{
  "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.
Roo Code settings
{
  "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.
kilo.jsonc
{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
kilo.jsonc with an assistant key
{
  "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.
webtzm.yaml
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.
Devin custom MCP
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, sign in
amp mcp add webtzm https://webtzm.com/mcp/workspace
settings.json
{
  "amp.mcpServers": {
    "webtzm": {
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
settings.json with an assistant key
{
  "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 CLI, sign in
gemini mcp add --transport http webtzm https://webtzm.com/mcp/workspace

To use a key, pass it as a header.

Gemini CLI, assistant key
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.

Qwen Code, assistant 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.

settings.json
{
  "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.
opencode.json
{
  "mcp": {
    "webtzm": {
      "type": "remote",
      "url": "https://webtzm.com/mcp/workspace"
    }
  }
}
opencode.json with an assistant key
{
  "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.
config.yaml
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.
Open WebUI connection
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.
mcp.json
{
  "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.
Cherry Studio server
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.

librechat.yaml
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 Your AI assistant, in the console's Setup."
        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.
anythingllm_mcp_servers.json
{
  "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.

SettingValue
TransportStreamable HTTP
URLhttps://webtzm.com/mcp/workspace
Header (key only)Authorization: Bearer YOUR_WEBTZM_KEY

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.

Generic settings
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.

Bridge, sign in
{
  "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.

Bridge, assistant key
{
  "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.

ToolWhat it doesNeeds View and make changes
get_workspaceShows the workspace name, its plan, this period's usage, and whether Google is connected.No
list_formsLists your forms with status, Google output, Sheet link, submissions this period, and the last submission time.No
get_formShows one form's questions with their settings, allowed sites, success message or redirect, anti-spam check, owner alert, and its Webtzm page settings, and lists what on the form stays in the console.No
get_form_embed_codeReturns the form's HTML for a site, with the rules for using it.No
list_recent_submissionsShows delivery status and anything that needs review, newest first, and pages back through older ones. Says whether each one added a row or changed or removed an entry's row, which entry, and when an entry was later removed. Never what a visitor typed.No
get_submissionShows one submission's delivery status: what it did to which entry's row, when it arrived and was delivered, and why it needs review if it does. Never what a visitor typed.No
create_formCreates a form that delivers to a new Google Sheet and returns its code. Questions can be any kind except file upload, and it can set up the form's Webtzm page. With Pro it can also make, in the same call, the forms and per-row links for editing and removing entries and turn on Record Fetch; it never creates a key.Yes
update_formChanges a form's name, questions and their settings, allowed sites, success message or redirect, anti-spam check, owner alert, or Webtzm page.Yes
set_form_statusPauses a form or makes it active again.Yes
allow_websiteAllows a website to send to a form and releases what was held from it. A submission from a website that is not on the form's list is kept, not delivered, until you allow it.Yes
retry_deliveryHands a submission that stopped, one that reads Needs review, back to delivery once the cause is fixed. It changes no delivered data, and a row that already landed is never written twice.Yes
create_linked_formCreates a form that changes or removes the rows another form added, and returns its code. Included with Pro.Yes
set_record_fetchTurns Record Fetch on or off for a form, with the columns and freshness you choose. It never creates or shows a key: you create one in the connection's Setup, under Advanced. Included with Pro.Yes
set_record_linksTurns edit or remove links on or off for a form that changes or removes rows, with Show current answers and Only accept changes from links, and writes them into the rows already there. It never shows a link. Included with Pro.Yes

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.

Webtzm Form through an assistant

An assistant can set up the public Webtzm page of a form, the link you send when you have no website to put the form on. Ask it to turn the page on and hand you the link, or to change the page the way the page editor would:

  • Turn the page on or off, and read its link.
  • Write the description and the button text, and choose a theme, colour mode and header alignment.
  • With Pro: the accent colour, corners, font, button, card, width and field style, a colour or gradient background, a thank-you heading, a footer line, a link preview, a closing date and a response limit.
  • Take a logo, cover or background picture off the page.
  • Make questions of any kind except file upload (text, email, phone, web address, number, date, time, long answer, drop-down, single choice, tick boxes, scale, star rating, slider, consent, ranking and choice grid), with their help text, limits and options, and put headings, text blocks and, with Pro, page breaks between them.

A change that needs Pro on a Free workspace comes back as a plain sentence naming what needs Pro, and nothing in that page change is saved. Leave those parts out, or upgrade under Account, Billing.

A link that opens the page with answers already filled in is the page's link followed by ?, the question's name, = and the answer. Hidden, file upload, consent and grid questions are never filled in, and nothing private belongs in a link.

Still in the console

Uploading a picture, and its crop, position and zoom: the form's Setup, Share, Open page editor, then Design. File upload questions, show-if rules and the rules that skip a page: the form's Setup, Questions, Edit questions. A page Webtzm has blocked: email support@webtzm.com. When you ask about a form, the assistant lists what on that form stays in the console and where to find it.

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. Record Fetch can be turned on, but its keys are made only in the console.
  • Read what visitors submitted. It sees delivery status, not the contents of a submission.
Why this is safe

A connection belongs to one workspace and one access level. Webtzm checks it again on every request, so removing someone from a workspace, or pausing the workspace for deletion, ends the assistant's access on its next call. You can disconnect any assistant, or revoke any key, from Your AI assistant in the console's Setup at any time.

Request limits

Each connection, and each access key, can make 30 requests per 60 seconds. Connections are counted separately, so one busy assistant does not slow another. Several tool calls sent together in one request count as one.

Past the limit, Webtzm answers with HTTP 429 and a Retry-After header giving the seconds to wait, which is 60. The body is a JSON-RPC error with code -32000 and the message rate_limited, carrying the id of each refused call so a client can match it. Nothing in a refused request is carried out, so wait and send it again.

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.”
Keep the form's code as it is

Ask the assistant to change the styling around the form, not the form itself. The field names and the hidden form field are what let Webtzm accept the submission.

Troubleshooting

The assistant says the site is not allowed

The page's site is not in the form's allowed sites, so Webtzm refuses submissions from it. Ask the assistant to add it, which needs View and make changes, or add it yourself as described in Allowed websites. Use the exact https address, such as https://www.example.com.

The client shows 401 or asks me to reconnect

Webtzm no longer accepts that connection. You may have been removed from the workspace, the workspace may be paused for deletion, or the connection was disconnected. Connect again, and check Assistants with access, under Your AI assistant in the console's Setup, to confirm it is listed.

My key stopped working

It was revoked, or it belongs to a different workspace. Check that the header reads Authorization: Bearer followed by the whole key with no extra spaces, then create a new key under Your AI assistant, in the console's Setup, if needed. A key cannot be shown again after it is created.

The assistant can read my forms but cannot change them

It was connected as View only. Disconnect it and connect again choosing View and make changes, or create a key with that access.

Requests are refused with 429 or rate_limited

The connection went over 30 requests in 60 seconds. Wait for the number of seconds in the Retry-After header and try again. See Request limits.

Analytics shows delivered submissions but no country for them

The map in Analytics places every accepted or held submission by the country of the network that sent it, read at Webtzm’s edge as the form posts. Nothing runs in the visitor’s browser, so a tracking or ad blocker changes nothing; a VPN or a company network places a submission where that network sits. A country appears once it has three submissions in the last 30 days - fewer are counted as a small group - and a submission the edge could not place is counted without a location. The coverage line on the card states both counts.

A new form is refused until Google is connected

Creating a form delivers to a Google Sheet, so Google must be connected first. Connect it as described in Sign in and connect Google, then ask again.

My client only supports local servers

Use the mcp-remote bridge from Local-only (stdio) clients.

My client only supports SSE

Run it through the mcp-remote bridge from Local-only (stdio) clients. The bridge presents Webtzm to the client as a local server.

Something missing or wrong on this page? Tell support.