MiniUp with Claude
Get started
Claude connects to the same MiniUp platform as other account-based AI clients.
- In Claude, open Customize → Connectors.
- Select +, then Add custom connector.
- Enter
https://www.miniup.io/api/mcpas the remote server URL. - Connect, sign in to MiniUp, and approve the access you need.
- Enable the connector in your conversation.
For managed workspaces, an owner may need to add the connector in Organization settings → Connectors first. See Anthropic’s current custom connector instructions .
Existing connections using https://www.miniup.io/api/claude/mcp keep working. You do not need to recreate them.
Start with “Publish this HTML,” “Show my MiniUp datasets,” or “Build a map from my approved Dataset Bundle.” Ask Claude to inspect your existing Site before editing it. MiniUp supports multi-file HTML, CSS, JavaScript, and assets and returns the exact published URL.
File transfer depends on what Claude makes available to the connector. MiniUp accepts an authorized HTTPS download URL through its general file workflow; a Claude-local attachment identifier alone is not a downloadable file. If transfer is unavailable, upload the dataset to MiniUp, then use its Data Catalog or a Dataset Bundle. Do not paste credentials into a file URL.
Compliant MCP Apps hosts can display MiniUp’s shared result UI. The structured result and exact links also work without embedded UI.
Interactive apps with Live
Ask for “Create a multiplayer Chess app and publish it on Miniup,” “Create a collaborative checklist,” or “Build a shared map where my team can add markers.” Ordinary website publication and spreadsheet dashboards do not need Live unless you request collaboration.
When listed in your client, get_miniup_live_capabilities discovers the official SDK, templates, recipes, and limits. Use create_miniup_live_app for an official template with a stable requestId and address. Retry with the same values; finish=true explicitly resumes activation. For custom apps, retrieve the actual recipe source, generate static HTML/CSS/JavaScript, use existing staging and publish_project_site, then configure_site_live with the matching mode and component. Settings require the current owner or a site administrator and preserve omitted guest/access preferences.
The assistant should report the real URL, activation status, outstanding setup, and invitation workflow. Open the app, start a room, and share its invitation. Live requires an eligible account and available page allowance; private app access still applies. “Ready” verifies configuration and eligibility; actual room admission is checked when you connect.
New tools on the published ChatGPT plugin require automated review. Only call tools actually listed by your client; deployment alone does not prove review approval. If Live tools are unavailable, open the published site’s dashboard → Miniup Live, or use Create Interactive App. Existing connections and publishing tools continue working; these tools reuse existing publishing and site-write permissions.
Shared counters use atomic increments. Shared objects require observed versions; preserve drafts on conflict. Transient events do not persist. Custom competitive games require supported trusted rules; never supply browser code as server rules. See the Live SDK documentation.