Support for per-workspace MCP config on Antigravity

Is possible to configure MCP servers per-workspace on Antigravity? There is some servers that i want to activate only in specific projects (like a Minecraft Wiki MCP i use for datapacks and mods) or i want to load them with specific settings per-project (like the filesystem MCP).

6 Likes

i am also interested in this feature.

1 Like

I am also interested in. Did you find how to do it ?

Suboptimal solution but still working for the moment:

Start the name of the same project mcp in the same way, and when start to chating just write “Use only the mcp’s that start by “common” or “project-name” and that works for the moment.

Thank you for your feedback. We appreciate you taking the time to share your thoughts with us, and we’ll be filing a feature request.
To help us prioritize this request effectively, any additional details you can provide regarding the impact this feature would have would be very helpful.

1 Like

Well, aside the possibility to have different configurations for certain MCP servers depending of the project, that would also prevent overloading the AI with not-needed MCP servers that are registered for other projects, and also reduce the risk of messing the gemini settings.json file (that i see that stores MCP information for both Antigravity, Gemini CLI and Gemini Code Companion).

2 Likes

I would also love to see this feature implemented. Having a per-workspace MCP configuration would significantly improve the developer experience by allowing us to isolate tools and contexts for different projects. Currently, managing a global config can get messy as projects grow.

Looking forward to seeing this in a future update. Thanks for the great work on Antigravity!

It is really essential thing. Kiro CLI/IDE and Claude already have this feature.