[BUG] Supabase MCP Connector InOp On New Session Creation Through Claude Dispatch

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When a new code session is created in Claude Desktop via Dispatch, the Supabase MCP connector does not work until the user manually opens the connector "+" menu at their desktop.

What Should Happen?

When a new code session is created via Dispatch, the new code session should have access to the already configured MCP connectors the same way that it does when a code session is manually created in Claude Desktop.

Error Messages/Logs

Dispatch response after telling it to double check Supabase connectivity of the new session:
Confirmed — same situation as before. Supabase MCP is not attached to this session. Session ran ToolSearch twice (supabase, supabase project) — no matches. The deferred tool list it sees has Claude_in_Chrome, computer-use, mcp-registry, scheduled-tasks, etc., but no mcp__9f527c03-...__* server. No error to surface; there’s just nothing to call.

Steps to Reproduce

1. Ensure that the Supabase MCP connector is properly configured in Claude Desktop, and that Claude Desktop is connected to Dispatch via the iOS application.
2. Instruct the Dispatch agent in the app to create a new code session that will perform a task requiring the use of the Supabase connector.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.138

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

1.7196.0 is the version of Claude Desktop, and I do not have the Claude Code CLI installed on my machine.