On this page
Connect an agent remotely
Copy the app’s connection URL from Agent Actions → Connect an agent remotely:
https://www.miniup.io/api/apps/your-app/mcpUse it as a remote MCP server in a compatible client. Public read actions may be available anonymously. Protected apps require MiniUp OAuth sign-in. OAuth clients use MiniUp’s existing registration, consent, PKCE, token, and refresh endpoints; each app has an exact resource audience. A token issued for Account MCP or another app cannot be reused as an app action token.
The endpoint uses the existing MiniUp MCP SDK and transport, supporting current 2026-07-28 negotiation and legacy clients. Its action definitions and execution service are shared with Web tools and dashboard testing.
OAuth scopes restrict what an authenticated client may use:
miniup.data.read: Table reads.miniup.data.write: Table mutations.miniup.functions.write: Function execution, which can have side effects even when its HTTP method is GET.
Scopes never grant site membership. Viewers cannot mutate; editors retain the existing editor role. Configure the app and source permissions in MiniUp before connecting.
The per-app metadata URL is /api/apps/your-app/mcp-metadata and is advertised in authentication challenges. Remote MCP accepts bearer credentials; it does not use browser cookies as account authorization. Browser-origin MCP requests are restricted to the MiniUp application origin.
MiniUp Account MCP manages and builds resources. App Agent Actions operates one published app. Existing Account MCP URLs and tools remain unchanged.