Google · Local and remote MCP servers, skills, plugins
How to add MCP servers to Antigravity CLI
Antigravity CLI (agy), which replaced Gemini CLI in June 2026, reads MCP servers from ~/.gemini/config/mcp_config.json (all projects) or .agents/mcp_config.json (one project), under mcpServers. Remote servers use serverUrl. Skills go in ~/.gemini/antigravity-cli/skills/ or .agents/skills/.
Add a local server
Edit ~/.gemini/config/mcp_config.json (all projects) or .agents/mcp_config.json (this project):
{
"mcpServers": {
"my-server": {
"command": "npx",
"args": ["-y", "some-mcp-package"],
"env": { "API_KEY": "your-key" }
}
}
}
Add a remote server
Use serverUrl. The old Gemini CLI keys url and httpUrl need renaming.
{ "mcpServers": { "my-server": { "serverUrl": "https://example.com/mcp" } } }
Skills
Put skill folders (each with a SKILL.md) in ~/.gemini/antigravity-cli/skills/, or .agents/skills/ for one project. Skills in an old .gemini/skills/ folder need moving to .agents/skills/.
Coming from Gemini CLI
The first time you run agy, it detects your old Gemini CLI settings. Old extensions, now called Antigravity plugins, are converted with:
agy plugin import geminiOfficial documentation
Antigravity CLI changes often. If a step here no longer matches, the official docs win.