Improvement suggestion: "profile" management to only activate a subset of MCP servers

[gmorain]

Hi,

thank you for giving this nice UI to the community!

As you probably have done so yourself, I tested a lot of MCP servers and sometimes the agent gets confused because multiple MCP servers have an overlapping set of tools (e.g. fetch / pupeteer / firecrawl) or need a specific configuration to be truly effective and focused (fileserver, postgres, git, ...).

What I have in mind is a "profile" which stores a list of enabled MCP servers with their custom config, allowing me to quickly switch between two profiles depending on which "task" I am working on.

Do you think it reasonably fits into the Fleur vision?

Best,
Gilles

[ferrucc-io]

Hey there I think this makes sense! Profiles would be particularly exciting if you could share them too so that one person on a team could share their "AI MCP workspace" with others