Exepad turns a conversation with Claude into a working website or web app that you own, hosted by Exepad at its own web address. Claude writes the app's code in your Exepad account, and Exepad keeps every change as a revision, builds it, gives you a private preview, and publishes a build only after you approve it in Exepad.
- Creates web apps in your Exepad account, and reads, searches and changes the source of the apps you connect.
- Builds each change and reports compiler errors, so Claude can fix them.
- Checks a build's private preview for console errors, exceptions and failed requests, and takes its screenshot.
- Where Claude shows Exepad's card in the conversation, the card holds the build's state, its latest screenshot and Open preview, which opens the private preview in Exepad.
- Publishes a build after you approve it in Exepad, and lists an app's releases.
- Renames an app, and unpublishes or archives one after you confirm it in Exepad.
The plugin holds one skill, build-an-app, which describes how Claude works with Exepad: reading Exepad's reference
first, changing the source in small steps, building and fixing until the build succeeds, checking the preview, and
asking you before anything goes live. It also names Exepad's server, https://mcp.exepad.com/mcp.
- You need an Exepad account. Every Exepad plan connects through Claude's connector.
- In Claude, add the plugin from Customize › Plugins. Adding it does not connect Exepad or sign you in: open the plugin, select its Connectors tab, and connect Exepad there. The Exepad connector is also listed on its own in Claude's directory, under Customize › Connectors › Browse.
- Sign in with your Exepad account, and choose the apps Claude may work on.
- Ask Claude, for example: "Build a habit tracker where I can tick off habits each day, then show me the preview."
Claude asks before every Exepad tool call until you choose Always allow (Customize › Connectors › Exepad › Tool permissions); setting Read-only tools to Always allow stops the prompts for reads.
Disconnect in Claude does not end the connection on Exepad's side. To end access, revoke Claude in Exepad › AI assistant plugins (https://app.exepad.com/assistants).
On a Claude Team or Enterprise plan, an Owner may need to allow Exepad first, in Organization settings › Connectors; members then connect with their own Exepad accounts.
Only if Claude does not offer the Exepad connector, add it yourself as a custom connector: in Customize › Connectors,
choose Add custom connector, name it Exepad and enter https://mcp.exepad.com/mcp.
The plugin runs no code of its own and stores nothing. Through the Exepad connector, Claude sends app source, and
build, preview and publish requests, to your Exepad account at mcp.exepad.com, and reads back the results: file
contents, build reports, preview checks and screenshots. Claude works only on the apps you choose when you connect
and the apps it creates through that connection. Nothing goes live until you approve a publish in Exepad. Exepad's
privacy policy is at https://exepad.com/privacy.
In Claude Code, the plugin's exepad server connects with its own sign-in, on every Exepad plan. Claude Code also
offers the Exepad connector you added on claude.ai when you sign in with the same Claude account; to keep one set of
Exepad tools, switch one of the two off in /mcp.
- Setup and documentation: https://exepad.com/ai-assistant-plugins
- Support: https://exepad.com/contact
- Security reports: support@exepad.com
The plugin is released under the MIT License (see LICENSE).