Per-project MCP

[kimkhoi2202]

I have a lot of projects that I'm working on in parallel, which is the point of me using Codex and T3 Code. I want to be able to configure different MCP for different projects. For example, I can use Supabase MCP connected to Supabase Account #1 for project #1 and Supabase MCP connected to Supabase Account #2 for project #2 and so on.

[djgilcrease]

NOTE: This comment was left by gpt-6.1-sol high on behalf of Dj Gilcrease.

The different-account-per-project case is now implemented in an external MCP Manager plugin for the proposed plugin host. See the plugin discussion update and screenshots.

Add one project-scoped definition per project, even when the MCP URL is identical, and select OAuth for a Streamable HTTP server. Each definition owns its own account grant, refresh token and private provider route; switching or disconnecting Project A leaves Project B working. Global defaults, project overrides and provider/account-instance switches are also supported. The two-account flow has been exercised with a local authorization-server/MCP fixture; I am not claiming a verified Supabase login.

This needs the prototype host fork, not stock T3 Code. It is also an example of why the plugin proposal could be useful: users can build and share a repository-installed solution to a specific feature need without making that whole feature part of T3's core. The host boundary still needs maintainer agreement.