On this page
Troubleshooting
No actions appear: Check the global switch, the selected interface, individual actions, publication state, and source API methods. Then reload the published app. The browser must support the current WebMCP draft; ordinary browsers continue to show only the app UI.
A Table operation is unavailable: Enable that operation in the Table API settings first. A mutation also requires an editor, admin, or owner. Creating an action never enables an underlying method automatically.
A Function is unavailable: Publish it, link it to this app, and configure Public, Site Member, or MiniUp User access. An API-key-only Function is not exposed without an eligible identity mode.
Invalid action input: Inspect the effective definition. Use actual field types, keep limits within range, and omit fields that are not in the schema. A source schema change can invalidate previously prepared input.
Invalid schema: Use the documented bounded schema subset with additionalProperties: false on every object. Remote references, recursion, regex patterns, and composition keywords are unsupported.
Remote authentication fails: Connect to the copied app URL and complete OAuth for that exact resource. Reconnect after token revocation or scope changes. An Account MCP token or another app’s token has the wrong audience. Ensure the signed-in account is a current member.
Planner unavailable: Use structured testing. AI planning depends on the configured provider, your AI Studio permissions, and your allowance.
Result too large: Narrow filters, request fewer records, or have the Function return a smaller application response.
Timeout or cancellation after a mutation: Inspect the application state before retrying. Cancellation does not undo a committed operation. The platform does not automatically retry writes.
Works on the MiniUp address but not a custom domain: Verify the domain is active, reload the page, and inspect CSP. The bootstrap uses the request host to resolve the app and never relaxes security policy.