Skip to main content
More visitors browse with an AI assistant built into their browser, such as ChatGPT’s browser. When a visitor asks the assistant for help with your product, the assistant usually reads your pages and guesses. With WebMCP, your chat widget gives the assistant a direct line to your Typewise support agent instead, so the answer comes from the same Specialists, knowledge, and actions that handle your chat tickets. WebMCP is a browser standard for websites to offer tools to AI assistants. Typewise registers these tools through the chat widget, so there is nothing to build on your side.

​
Before you start

  • The chat widget is installed on your website. See Installation.
  • Your company name is set in General behaviour. Assistants use it to refer to your support, and it prefixes the tool names. WebMCP can’t be enabled without it.

​
Enable WebMCP

1

Open WebMCP

Go to WebMCP under chat installation.
2

Turn it on

Switch on Enable WebMCP. The change saves right away and reaches your website within a few minutes.
Turn it off the same way. The widget then stops offering the tools on the next page load.

​
What the assistant can do

The widget registers four tools, prefixed with your company name in lowercase with underscores. For a company named “Acme Shop”, the prefix is acme_shop. The tool description tells the assistant what your support covers. Typewise builds it from your published Specialists and actions, so you don’t maintain it separately. Publish changes to update it.

​
How conversations are handled

Questions from an assistant create regular chat tickets. They follow the same Specialists, guidelines, and handoff conditions as tickets from the chat widget, and they’re marked with a robot icon in the inbox.
  • Account-specific requests need a verified email, the same as in the chat widget. The assistant asks the customer for their email and the code they receive.
  • Handoffs go to your team as usual. The assistant tells the customer that a person is looking into it, and your team replies by email.

​
Troubleshooting

The assistant doesn’t see the tools:
  • Check that Enable WebMCP is on and that your company name is set in General behaviour.
  • Check that the chat widget loads on the page. The tools come from the widget, so a page without it, or a domain blocked by the Domain allowlist, offers none.
  • Check that the assistant’s browser supports WebMCP. In other browsers, the widget works as usual and offers no tools.

​
See also