One-click install of the Latitude MCP server inside Google Antigravity.
After installing and authorizing, Antigravity can read and manage your Latitude workspace: projects, members, keys, traces, annotations, scores, searches, issues, datasets, and more. The full tool catalog is dynamically generated from the Latitude API.
Browse the Customizations page inside Antigravity and add Latitude from the bundled plugins list (once published).
Antigravity scans for plugins in three locations — pick the one matching your scope:
| Scope | Path |
|---|---|
| Workspace | <workspace>/.agents/plugins/latitude/ (or _agents/plugins/) |
| User-global (Antigravity editor) | ~/.gemini/config/plugins/latitude/ |
| User-global (Antigravity CLI) | ~/.gemini/antigravity-cli/plugins/latitude/ |
# Global install (from a clone of this repo):
mkdir -p ~/.gemini/config/plugins
cp -R . ~/.gemini/config/plugins/latitudeRestart Antigravity. The plugin is auto-discovered, and the Latitude MCP server appears in the Customizations tab. Click Authenticate to start the OAuth flow (Antigravity handles Dynamic Client Registration automatically — no client ID/secret needed).
Skip the plugin and edit ~/.gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"latitude": {
"serverUrl": "https://api.latitude.so/v1/mcp"
}
}
}Then Agent Settings → Customizations → Authenticate next to latitude.
.
├── plugin.json # Plugin manifest (marker file + metadata)
├── mcp_config.json # Latitude MCP server config (serverUrl + DCR)
├── assets/ # Icons
├── LICENSE
└── README.md
No skills/, rules/, or hooks.json — this plugin only registers the MCP server.
Third-party plugin submission to Antigravity's bundled marketplace ("Build with Google") goes through Google partnership. There is no self-serve publishing flow documented yet, so the primary distribution path today is users manually copying the antigravity/ folder into one of the locations above. Track the Antigravity docs for changes.