supabase / mcp / 35209363812

97%

push

github

feat(mcp)!: confirm destructive SQL via elicitation and rename costConfirmation option (#408)

## Why

Adds confirmation elicitations before destructive SQL, such as dropping
a table

Closes [AI-1186](https://linear.app/supabase/issue/AI-1186).

## What changed

- Renames `costConfirmation` → `confirmation`. `enabledTools` 
- Supports existing cost confirmations (`create_project`,
`create_branch`) and SQL confirmations (`execute_sql`,
`apply_migration`);
- Local HTTP opts into both SQL tools. 
- No new dependencies.

## How to test
<details>
<summary>Expand for details</summary>

1. **Choose one disposable target and prepare your tools.** Use either:
- **Staging:** API `https://api.supabase.green`, an existing staging
personal access token (PAT), and a disposable staging project ref.
- **Dedicated disposable production:** API `https://api.supabase.com`,
an existing production PAT, and that disposable production project's
ref.

The server API URL, PAT, and project ref must all match your choice.
**Never use customer, shared, or application data.**

Check out this PR (`feat/destructive-sql-confirmation`, reviewed head
`8a7e9de`) locally. Have the repository's Node LTS and pnpm 10 active
([tool
setup](https://github.com/supabase/mcp/blob/a4f435165/CONTRIBUTING.md)),
plus a current Claude Code version with MCP elicitation form support.
Disable elicitation auto-answer hooks for this session.

2. **Build and start the local HTTP server in Terminal A.** Replace
`/path/to/this-pr-checkout` with your checkout root: the folder
containing `package.json` and `packages/`.

Use your existing pnpm 10.33.2 executable: replace `PNPM10` below with
its absolute path before running. The subshell puts it ahead of Corepack
shims so nested commands use the same version, without changing your
shell configuration. No `approve-builds` step is needed;
`enable-pre-post-scripts` enables the package’s own prebuild step, not
dependency build approval.... (continued)

564 of 604 branches covered (93.38%)

Branch coverage included in aggregate %.

439 of 453 new or added lines in 8 files covered. (96.91%)

3745 of 3847 relevant lines covered (97.35%)

78.15 hits per line