MiniUp with other MCP clients
Get started
Use https://www.miniup.io/api/mcp for account access. MiniUp supports MCP 2026-07-28 and compatible 2025-era clients over Streamable HTTP. Your client discovers the sign-in flow; sign in and approve the requested permissions.
Site publishing, Site management, data reads, data changes, usage, and Function management have separate permission groups. Reconnect when a new operation needs access you have not approved. A client label never changes your permissions.
Discover tools for publishing HTML and multi-file projects, reading and updating Sites, managing Table records, inspecting datasets, using Dataset Bundles, and working with safe Functions. The workflow guide and capability resource help your assistant choose a path. Use the same requestId when retrying a Site publication.
Use an authorized HTTPS file URL or supported file content in the general file workflow. A local path or client-local attachment identifier is not remotely accessible. File upload features differ between clients. Hosted MiniUp datasets and bundles are another starting point.
The standard MCP Apps result resource provides a shared UI in supported hosts. Text and structured results are available in every supported client. Manage saved secrets and secret-bound Functions in MiniUp.
For paid wallet-owned work, use the separate x402 connection.
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.