All plugins

webtwizz

Build, change and publish websites and web apps with WebTwizz through its hosted MCP server (https://app.webtwizz.com/mcp, OAuth sign-in in the browser, no keys in config): landing pages, online stores, booking sites, portfolios and web apps with sign-ins and a database, published to a webtwizz.app address or the user's own domain, with version history, site data and GitHub sync. Agent Plugins v1 package (plugin.json + mcp.json), configuration only. Disclosure: every tool call goes to WebTwizz's hosted server (app.webtwizz.com) and acts on the user's WebTwizz account; the tool set is served by that server at runtime and is not covered by the pinned sha. Builds and edits spend WebTwizz credits, and publish-site only returns a link: the site goes live when the user presses Publish in the WebTwizz editor. Sign-in runs the pinned mcp-remote@0.1.49 through npx (Node.js and npm required), which opens a browser and a local callback port on first use and stores OAuth tokens under ~/.mcp-auth. The package marks the server untrusted, so Hermes asks before every tool the server does not mark read-only and refuses them in unattended runs.

WebTwizzToolsv1.0.0Updated 3 hours ago

About

Build, change and publish websites and web apps with WebTwizz through its hosted MCP server (https://app.webtwizz.com/mcp, OAuth sign-in in the browser, no keys in config): landing pages, online stores, booking sites, portfolios and web apps with sign-ins and a database, published to a webtwizz.app address or the user's own domain, with version history, site data and GitHub sync. Agent Plugins v1 package (plugin.json + mcp.json), configuration only. Disclosure: every tool call goes to WebTwizz's hosted server (app.webtwizz.com) and acts on the user's WebTwizz account; the tool set is served by that server at runtime and is not covered by the pinned sha. Builds and edits spend WebTwizz credits, and publish-site only returns a link: the site goes live when the user presses Publish in the WebTwizz editor. Sign-in runs the pinned mcp-remote@0.1.49 through npx (Node.js and npm required), which opens a browser and a local callback port on first use and stores OAuth tokens under ~/.mcp-auth. The package marks the server untrusted, so Hermes asks before every tool the server does not mark read-only and refuses them in unattended runs.

WebTwizz for Hermes Agent

Build, change and publish websites and web apps with WebTwizz from Hermes Agent: landing pages, online stores, booking sites, portfolios and web apps with sign-ins and a database. Publish to a webtwizz.app address or your own domain, undo changes, edit site data and sync with GitHub.

Install

hermes plugins install webtwizz

The first WebTwizz tool call opens a browser to sign in to WebTwizz or create a free account. Nothing is configured by hand and no API key is stored in this package. The account needs a verified email address before WebTwizz can build or change anything.

What to ask for

  • "Build me a site for my bakery with a menu, opening hours and a contact form."
  • "Show me WebTwizz templates for a photography portfolio."
  • "Change the big heading on my bakery site to 'Fresh bread every morning'."
  • "Publish my bakery site."

Builds take from a few seconds to several minutes. get-site shows when a change is finished. publish-site never publishes on its own: it returns a link that opens Publish in the WebTwizz editor, and the site goes live when you press it.

What this package does

  • Configuration only. It holds plugin.json and mcp.json and no code of its own. The tools are served at runtime by WebTwizz's hosted MCP server at https://app.webtwizz.com/mcp and are not covered by the pinned commit.
  • Network: every tool call goes to app.webtwizz.com and acts on your WebTwizz account. Builds and edits use WebTwizz credits, the same as in the WebTwizz editor.
  • Sign-in: runs the pinned mcp-remote@0.1.49 through npx (Node.js and npm required). On first use it opens a browser and a local callback port, and it stores the OAuth tokens under ~/.mcp-auth.
  • Approvals: the package marks the server untrusted, so Hermes asks before every tool the server doesn't mark read-only, and refuses them in unattended runs.
  • Disconnect: in WebTwizz, open Settings, then Sessions, and remove Hermes Agent under Connected apps. Deleting ~/.mcp-auth removes the local tokens.

Links

README from the reviewed commit e197928; it updates when the author re-pins.