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).
15 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!
1 Like
It is really essential thing. Kiro CLI/IDE and Claude already have this feature.
3 Likes
For security reasons, when working for multiple clients or multiple unrelated projects, having an MCP with a specific connection is a priority both for application security and to avoid knowledge mixing.
2 Likes
While waiting for native per-workspace support, one workaround is running a proxy between Antigravity and your MCP servers. You configure all your servers once in the proxy, and Antigravity just points at a single endpoint. Switching projects is handled automatically by the proxy — no need to touch IDE or proxy settings. This also means your config stays the same if you switch between Antigravity and other editors. GitHub - smart-mcp-proxy/mcpproxy-go: Supercharge AI Agents, Safely handles this pretty cleanly.
But how proxy knows request comes from “folder A” or “folder B” to route to correct mcp(s), the mcp_config is global. How exactly it’s handled on the proxy side?
This is a critical feature for our workflow. We have a game engine and each project has a unique mcp server. Other tools like Claude Code and Codex read our mcp.json file so we can match each project opened with its engine MCP server (isolated for security).
Antigravity does not support this, so we have to constantly manually adjust the config for testing, and its non-tenable for our end users. We have to recommend other tools.
Hello @Matt_Salsamendi, welcome to AI Forum!
Thank you for sharing your feedback. Please be assured that I have shared this with our internal team for further review.
We appreciate your continued patience as we work to enhance the Antigravity experience.
1 Like