Skip to main content
Version: 3.0

Antigravity

Give Antigravity access to MaestroHub through its MCP server, using a Personal Access Token and your workspace ID.

Config file
~/.gemini/antigravity/mcp_config.json
Endpoint
/api/v1/mcp
Scope
Global, all projects

Antigravity supports MCP servers via a global configuration file.

Configuration​

Save the following as ~/.gemini/antigravity/mcp_config.json:

{
"mcpServers": {
"maestrohub": {
"serverUrl": "https://<your-instance>/api/v1/mcp",
"headers": {
"Authorization": "ApiKey <your-token>",
"X-Workspace-ID": "<your-workspace-id>"
}
}
}
}

Replace the placeholders:

  • <your-instance>: your MaestroHub domain (e.g., maestro.example.com)
  • <your-token>: the Personal Access Token you created
  • <your-workspace-id>: your workspace ID (found in the URL or workspace settings)
note

For local deployments without TLS, change https:// to http:// in the URL (e.g., http://localhost:6163/api/v1/mcp).

Tips​

  • Antigravity uses serverUrl instead of url in its MCP configuration.
  • The config file is global (~/.gemini/antigravity/), so MaestroHub will be available in all projects.
  • Create the directory if it doesn't exist: mkdir -p ~/.gemini/antigravity.