fusebase-gate

First verify the fusebase-gate MCP server is connected by checking for tools like tools_list, tools_search, and bootstrap. Then read the connection context resource or call bootstrap, discover operations with tools_search, inspect schemas with tools_describe, and execute with tool_call.

Call createAppMagicLink with the org id and the product id from fusebase.json as the appId path segment, not an app id from fusebase app list. The response returns id, magicLinkUrl, and expiresAt only for new accounts or previously activated recipients.

Use MCP tools for actions inside the LLM session such as discovery and token management. Use the @fusebase/fusebase-gate-sdk npm package in runtime application code, keeping direct typed API method calls so permission sync static analysis detects operations.

The appId path segment must be the product id from fusebase.json, not an app id from fusebase app list. The Gate wire contract uses pre-rename field names, so mixing product and app identifiers is the most common cause of this 404.

Token permission validation is soft by default: Gate degrades requested permissions to the allowed subset and ignores unknown permissions rather than failing. Strict mode is available only for explicit fail-fast requirements.

Do not use it for dashboard schema, rows, or files cell payload guidance; load the fusebase-dashboards skill instead. For the canonical low-level upload lifecycle, use the file-upload skill's upload-lifecycle reference.