The MCP can create disposable branches and run execute_sql, but it cannot provide a secret-safe way for a local test process to connect directly to the branch as a scoped PostgreSQL role.
The current workaround is to generate a temporary password and submit it inside ALTER ROLE ... PASSWORD through execute_sql. MCP clients may retain the complete resolved tool invocation, causing that plaintext password to remain in session metadata even when it is never printed or returned to the model.
This blocks database integration tests that must use native PostgreSQL connections—such as Psycopg or LangGraph checkpointers—to verify real role identity, TLS, ACLs, transaction behavior, and restart persistence.
Requested behavior
A connection template without the credential would also be useful if the MCP client can securely inject its existing OAuth/PAT credential into a local process.
No active credentials or production data are involved in this report.
Supabase already supports passwordless, role-scoped temporary access—including branches—so this requests MCP integration with that capability. (Temporary Access documentation)
Samriddhi Sinha requests a feature to integrate Supabase Temporary Access with MCP for secret-safe PostgreSQL connections. The current workaround involves generating temporary passwords, which poses security risks. The user suggests scoping access to specific branches and roles with short TTLs, and delivering credentials through secure channels. This would aid in database integration tests requiring native PostgreSQL connections.