Skip to content

Per-project MCP #276

@Xenoifyteam

Description

@Xenoifyteam

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.

If this is a feature, I don't care what state T3 is at (as long as it's stable), I'm willing to pay $200/month to use T3 Chat because of how much time it will save me from disconnecting and connecting new MCP every time I switch project. This is the main blocking point stopping me from working on multiple projects at the same time, utilizing the full power of Codex.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions