Connect the Silverile MCP server to Google Antigravity by manually editing mcp_config.json. This approach bypasses the interactive browser OAuth flow, which can cause connection timeouts or IDE UI errors, and lets you authenticate directly with your Silverile Bearer token.
Before you start, generate your Silverile Bearer Token — a base64url-encoded string that bundles your API key and workspace into a single credential.
ide_XXXXXXXXXXXXXXXX) and the Key SecretOpen your Silverile project and go to Project Settings. The Product ID is listed there as a number (e.g. 1424).
Run the following command in a terminal, substituting your own values. It produces a URL-safe base64 string with no padding:
echo -n '{"keyId":"ide_XXXXXXXXXXXXXXXX","keySecret":"your_key_secret_here","productId":12}' \
| openssl base64 -A \
| tr '+/' '-_' \
| tr -d '='eyJrZXlJZCI6... — is your Bearer Token. Copy it and use it in Step 2 below.You can access the configuration file in two ways:
mcp_config.json directly in the editorOpen the file directly in your preferred text editor:
| Platform | Path |
|---|---|
| macOS / Linux | ~/.gemini/antigravity/mcp_config.json |
| Windows | %USERPROFILE%\.gemini\antigravity\mcp_config.json |
Add the silverile entry under the mcpServers object in the JSON file, replacing YOUR_SILVERILE_BEARER_TOKEN with the token you retrieved above:
{
"mcpServers": {
"silverile": {
"serverUrl": "https://mcp.silverile.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SILVERILE_BEARER_TOKEN"
}
}
}
}serverUrl — Antigravity does not support the standard url key for remote HTTP / SSE servers.mcp_config.json fileOnce successfully connected, you will see a green dot next to silverile and all of its tools will be available to the agent.
Green dot never appears after saving
Click the Refresh button in the Installed MCP Servers view. If it still does not turn green, fully restart the Antigravity IDE to reload the backend connection.
Connection rejected or 401 errors
Confirm you pasted the full Bearer token with no extra whitespace. The token is a Base64-encoded string — regenerate it from your Silverile account under Settings → IDE API Keys if you are unsure.
Config key not recognised ("url" not supported)
Antigravity requires the key to be spelled exactly as serverUrl (not url). Check your mcp_config.json and correct the key name.
mcp_config.json file not found
The file may not yet exist if you have never configured an MCP server. Create it at the path shown in Step 1 with the JSON structure from Step 2.
Tools not visible after a successful connection
Go back to the Installed MCP Servers view and click Refresh. If tools are still missing, disconnect and reconnect the server.