Cost confirmations do not appear in your MCP client
Last edited: 10/14/2026
当你的连接使用费用确认对话框时,Supabase MCP 服务器会在 create_project 或 create_branch 创建会产生费用的资源之前,通过你的 MCP 客户端要求确认。如果你本来应该看到确认对话框但没有看到,可以按照这些检查步骤排查问题。
🌐 When your connection uses cost confirmation dialogs, the Supabase MCP server asks for confirmation through your MCP client before create_project or create_branch creates a resource that incurs charges. If you expect a confirmation dialog and don't see one, work through these checks.
你的客户使用 get_cost 和 confirm_cost#
🌐 Your client uses the get_cost and confirm_cost flow
当服务器为工具提供基于表单的费用确认,并且你的客户端支持请求的表单提示时,会出现费用确认对话框。仅凭规范修订本身并不能决定你的连接使用哪种流程。如果基于表单的费用确认不可用或不受支持,工具会改用传统的费用确认流程。在那个流程中,代理会在聊天中报出费用,并在创建资源前询问你。不会出现对话框,这是预期行为。
🌐 Cost confirmation dialogs appear when the server offers form-based cost confirmation for the tool and your client supports form elicitations for the request. The specification revision alone does not determine which flow your connection uses. If form-based cost confirmation is unavailable or unsupported, the tool uses the legacy cost confirmation workflow instead. In that workflow, the agent quotes the cost in chat and asks you before creating the resource. No dialog appears, and this is the expected behavior.
要检查一个创作工具使用的是哪种流程,可以让你的客户列出可用的 Supabase 工具,以及 get_cost 和 confirm_cost 接受的资源类型。这些助手接受的资源类型使用的是传统的成本确认流程;另一种资源类型则可以在同一个连接上使用基于表单的成本确认。它们的缺失并不能证明基于表单的成本确认已启用:项目范围、账户功能设置或服务器可用性也可能导致它们不可见。
🌐 To check which flow a creation tool uses, ask your client to list the available Supabase tools and the resource types accepted by get_cost and confirm_cost. The resource types accepted by these helpers use the legacy cost confirmation workflow; another resource type can use form-based cost confirmation on the same connection. Their absence does not prove that form-based cost confirmation is active: project scoping, account feature settings, or server availability can also hide them.
这个工具会跳过成本确认 #
🌐 Cost confirmations are skipped for the tool
检查你的 MCP 服务器 URL 是否为 skip_elicitations。如果包含 create_project 或 create_branch,该工具会使用旧的费用确认流程,而不是确认对话框。跳过表单并不意味着批准费用或避免收费。详见 跳过表单确认。
🌐 Check your MCP server URL for skip_elicitations. If it includes create_project or create_branch, that tool uses the legacy cost confirmation workflow instead of a confirmation dialog. Skipping the form does not approve the cost or avoid charges. See Skip form confirmations.
这个项目创建报价为零成本 #
🌐 The project creation is quoted at zero cost
当一个新项目创建请求使用基于表单的费用确认并且报价为零时,不会请求确认,项目会直接创建。这个例外不适用于分支创建:当它使用基于表单的费用确认时,会要求你在应用任何津贴或豁免之前确认标准费率。
🌐 When a new project creation request uses form-based cost confirmation and is quoted at zero cost, no confirmation is requested and the project is created directly. This exception does not apply to branch creation: when it uses form-based cost confirmation, it asks you to confirm the standard rate before any allowances or exemptions are applied.
你的客户端会自动回答提问 #
🌐 Your client answers elicitations automatically
有些客户端支持在不显示对话框的情况下响应提示的钩子或规则。如果在支持对话框的客户端上创建资源时没有看到可见的确认,请检查你客户端的提示或钩子配置。
🌐 Some clients support hooks or rules that respond to elicitations without showing a dialog. If resources are created without a visible confirmation on a client that supports the dialog, check your client's elicitation or hook configuration.
还卡住吗? #
🌐 Still stuck?
如果这些都不能解释你看到的情况,请在 Supabase MCP 仓库 上提交一个问题,并附上你的客户端名称和版本。
🌐 If none of these explain what you're seeing, open an issue on the Supabase MCP repository with your client name and version.