“Create an FAQ about shipping with five questions, then tell me how to add it to WordPress.”

Your AI becomes a widget builder

The Webynize MCP server gives an assistant access to your customer account and the published widget catalog. It writes the widget content you describe. It does not sync a social network.

Just ask

Describe the widget in plain English. The assistant picks the type, names it, and fills in the questions, quotes, plans, or other items.

The live catalog

Every published type, from tooltips and announcements to booking, store locators, timelines, and quizzes. Search works before you connect a key.

One URL

Point Cursor, Claude, or ChatGPT at the MCP server and paste the API key from your account. No SDK to install.

Paste steps included

Ask how to add it to WordPress, Shopify, Wix, Squarespace, Webflow, and the other supported builders.

Knows your plan

Before it creates a widget, it can check your limit and whether branding stays on. A full or expired account gets a plain explanation.

Manages what you have

List widgets, change settings, file one under a project, or read signups, quiz leads, and orders. Deletes wait for your confirmation.

Connect in three steps

1

Create a free account

Sign up at app.webynize.com if you don’t have one yet.

2

Generate your API key

In the app, open Settings, then API Key, and generate a key. Copy it then. It is shown once.

3

Add the server

Paste the setup for your client below, then describe the widget you want.

Endpoint https://mcp.webynize.com/mcp Key Settings → API Key

ChatGPT

ChatGPT can’t send a custom header, so the key goes in the link. Turn on Developer mode, add a custom connector, and set authentication to None.

https://mcp.webynize.com/mcp/YOUR_WEBYNIZE_API_KEY

A key contains |, which is not allowed in a URL. The link on your API Key page already writes it as %7C.

Cursor

Settings → Tools & MCP → add a server with this configuration.

{
  "mcpServers": {
    "webynize": {
      "url": "https://mcp.webynize.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_WEBYNIZE_API_KEY"
      }
    }
  }
}

Claude Code

Run this once in your terminal.

claude mcp add --transport http --scope user webynize https://mcp.webynize.com/mcp --header "Authorization: Bearer YOUR_WEBYNIZE_API_KEY"

Gemini

Gemini only asks for a server URL, so the key goes in the link. Add a custom connector and paste this as the MCP server URL. Encode | as %7C.

https://mcp.webynize.com/mcp/YOUR_WEBYNIZE_API_KEY

Grok

Open Settings, then Connect Apps, then Add MCP Server. Name it Webynize, paste this as the Server URL, and leave Headers empty.

https://mcp.webynize.com/mcp/YOUR_WEBYNIZE_API_KEY

Other MCP clients

Codex, VS Code, and Windsurf need the URL and a bearer header.

URL:    https://mcp.webynize.com/mcp
Header: Authorization: Bearer YOUR_WEBYNIZE_API_KEY

What the assistant can do

Catalog tools work with no key. Account tools need the customer API key. Staff accounts are refused. The full reference is on the API page.

ToolKeyWhat it does
search_widget_typesNoSearch published widget types by name or description.
get_widget_typeNoOne type: embeds, item fields, and templates.
get_create_requirementsNoThe name and type id create_widget needs.
get_embed_instructionsNoPaste steps for WordPress, Shopify, Wix, Squarespace, Webflow, Elementor, Framer, Ghost, HubSpot, Google Sites, or HTML.
create_widgetYesCreates the widget and returns the embed code and customize link.
get_account_statusYesPlan, widgets used, limit, and whether branding stays on.
list_widgetsYesThis account’s widgets, newest first. Filter by type, project, or name.
list_projectsYesThis account’s projects and the widgets in each one.
get_widgetYesOne widget, its settings, its items, and its embed code.
update_widgetYesChange the name, settings, branding, or project. Live without a re-paste.
add_widget_itemYesAdd a question, quote, plan, or other item this type stores.
update_widget_itemYesChange one item on a widget you own.
delete_widget_itemYesRemoves one item after confirm: true.
delete_widgetYesDeletes the widget after confirm: true. It stops on every site that embeds it.
list_widget_responsesYesRead email signups, quiz leads, or online orders. Nothing is deleted.

Prompts that work

“Create a testimonial widget named Customer stories and add three quotes.”

“How do I add this to Shopify?”

“List my widgets and file the FAQ under the Homepage project.”

“Show me the emails collected by my signup form.”

“What widget types does Webynize have for a pricing page?” — no key required.

What you get back

<div class='wbnz-faq' data-webynize-id='123'></div>
<script defer src='https://widgets.webynize.com/faq.js'></script>

The same snippet works on every builder that allows custom HTML. Some types also offer an iframe or a hosted link. The customize page is https://app.webynize.com/update-widget/123.

If the account is full, the trial has ended, or the key is missing, the assistant explains that instead of failing silently. Free accounts keep the Webynize badge on.

Questions

Which assistants work?

Any client that speaks MCP: ChatGPT, Cursor, Claude, Claude Code, Codex, VS Code, Gemini, Grok, and Windsurf.

Do I need to code?

No. You describe the widget. The assistant returns the embed code and the steps for your site.

Does MCP cost extra?

No. It uses your Webynize account, so the same plan and widget limit apply. See pricing.

Can it delete a widget by accident?

delete_widget and delete_widget_item do nothing unless the call includes confirm: true, after you agree.

Who can connect?

Customer accounts. Admin, support, content creator, and designer keys are refused, including for search.

Is the key safe?

It only reaches this account. Revoke it or generate a new one any time from Settings → API Key. A login session token is not an API key.