Skip to main content
Widgetic runs one public Model Context Protocol (MCP) server. Connect an AI assistant to it and you can describe a widget in plain words, watch it being built, publish it and get the code to put it on a website, without leaving the conversation.
That address is the whole setup: every supported assistant uses the same one.

​
What you can ask for

Build

“Make a countdown to our launch on March 3, in our brand green.” The assistant starts the build and shows you the preview as it comes together.

Change

“Make the numbers bigger and add a title.” Changes that need new code are rebuilt, and the new version replaces the one your embeds show (ask for a draft to try it first); texts, images, colors, fonts and sizes of a published widget change at once.

Publish and embed

“Give me the React component for it.” A finished widget is already published, so its embed code is ready: plain HTML, an iframe, or React, Vue, Svelte and Angular code. To look at a widget before it goes live, ask the assistant to keep it as a draft; publishing it later is a separate step.

Find, reuse and manage

“Show my drafts.” “Save these logos to my media library and use the first one.” “Go back to the previous version.” “Copy this widget for the pricing page.” The assistant can also rename or delete a widget (deleting asks you to confirm its title) and tell you how many credits you have left.

Plan a page or a workflow

“I want a landing page for my basketball team. Which widgets would work?” The assistant suggests the widgets that fit (a scoreboard, a schedule, a gallery, cards for the players), asks a few questions if it needs them, and starts the ones you choose together, each in its own canvas.

​
How it works

1

Describe the widget

The assistant calls create_widget with your description. The build starts and returns at once, usually finishing within a few minutes.
2

Watch and review

show_widget displays the build progress and then the live preview (as a card in assistants that can show one, as text otherwise). Ask for changes with revise_widget.
3

Publish, or keep a draft

A finished build is published for you, unless your plan does not include publishing, you approved the connection without the permission to publish, or you asked to keep it as a draft. publish_widget makes a kept draft live, or brings an earlier version back. It is only called after you agree, because it replaces what existing embeds show.
4

Customize and embed

update_widget_customization changes the texts, images, colors, fonts and sizes of a published widget without rebuilding it. get_embed_code returns the code and a share link.
For a page or a workflow made of several widgets, ask which widgets the assistant would suggest. It answers with a list, you choose, and it starts the chosen ones together (up to 25 at a time), after telling you how many credits that is. See Several widgets at once. With published widgets you can also ask for a workflow: widgets chained on one embed, so that a visitor who sends a form sees the thank-you card next, in the same place. The assistant writes it for you, tries it with made-up visitors, and publishes it only after you have seen it tried. See Workflows. On plans that include them, you can A/B test two to four published widgets on one embed and read which reaches a goal, or translate a widget into several languages on one embed. Both work in the workspace you are signed in to on widgetic.com (Teams, or a partner agreement). See A/B tests and Translations. The full list of tools is in the tools reference.

​
What it costs

  • Creating and revising a widget uses 1 credit per call, charged when the build starts. Starting several at once uses 1 credit per widget, charged as each build starts, and the assistant tells you the total before it starts them.
  • Everything else (suggesting which widgets to build, previews, listing, versions, copies, renaming, deleting, customization, embed code, workflows, A/B tests, translations, the media library, checking your usage) uses no credits. Saved files count against your storage allowance.
  • Publishing needs a plan that includes it and a connection approved with the publish permission. If either is missing, builds stay drafts and the assistant tells you.

​
What you need

  • A Widgetic account whose plan includes API access. Without it the connection is refused with a message saying so.
  • New widgets are made in the workspace you are signed in to on widgetic.com, your own or a team’s. In a team your role has to allow making widgets there, the credit is still your own, and the team’s Brand Kit applies. See Where a new widget goes.
  • To chain widgets into workflows, a plan that includes workflows, and the workspace you are signed in to on widgetic.com (your own or a team’s) is the one they are made in.
  • For A/B tests and translations, a plan that includes those features (Teams, or a partner agreement), in the same workspace.
  • An assistant that supports remote MCP servers. See Connect your assistant for ChatGPT, Codex, Cursor, Claude Code and VS Code.

​
Good to know

When your request needs it (a vote, a rating, a comment, an RSVP or a sign-up), the assistant can build a widget that keeps what its visitors send. Widgetic stores those entries in the widget’s own database in your account, and the widget can show the results (a poll’s tally, an average rating). You can ask the assistant for them whenever you like: counts per option by default, and the entries themselves only when you ask. A visitor can send more than once, and entries are not emailed or forwarded anywhere. The entries are yours: you can export or delete them through the REST API or the CLI (the assistant itself only reads them), and they are deleted with the widget. Orders, payments and logins are not built. A widget made from a pasted widget link keeps nothing, and neither does one you did not ask to keep entries (a quiz, a countdown, a gallery, a chart or a calculator only displays information).
Each create_widget call starts a separate widget and charges credits. A repeat of the same title within two minutes returns the widget already started and charges nothing, so a retry after a lost answer does not build twice; the same goes for each widget of a batch started with create_widget_batch. If a call times out, ask the assistant to check your widget list before it tries again.
delete_widget removes a widget for good, with all its versions and published copies; embeds already placed on websites stop working, and it cannot be undone. The assistant has to pass the exact title you confirmed, and a widget that is still being built cannot be deleted. Going back to an earlier version never deletes anything: list_widget_versions and publish_widget do that.
delete_media_file removes one file from your media library for good and gives its space back to your storage allowance. A widget that loads the file stops showing it, so the assistant is told which widgets use it and the file is refused until you say you still want it gone. Widgetic cannot see inside widgets built before it kept a record of which file went into which widget, so it never says that a file is unused. The assistant has to pass the exact file name you confirmed. Renaming or moving a file with manage_media_library is safe for your widgets: the file’s address does not change.
Besides a description, a build can start from up to 5 attached files (images, videos, PDFs, data files such as CSV, JSON or Excel, and Markdown or text files) and up to 3 Figma links. Figma links are read with your own connected Figma account, which you connect once from the Design page. See what a build can start from.
Requests to create or revise a widget are checked with a content moderation service before they are acted on, and so are the words you use to ask which widgets to build. Those words are also sent to a language model, which writes the suggestions. See the privacy policy for what is sent and why.

Connect your assistant

One snippet per client.

Tools reference

Every tool, what it costs and what it needs.

Authentication

Sign-in, API keys and revoking access.