Connect Google Antigravity to Rivul MCP
Connect Google Antigravity to Rivul MCP for AI research-paper search, citation metadata, usage checks, and revocable access.
On this page
Overview
Google Antigravity connects to Rivul MCP as a remote MCP server and signs in through its native Authenticate handoff. Its agent can then call search_papers, get_paper_details, and usage_status, all read-only.
Before you start
- Step 1: Use a Rivul AI account with Rivul MCP provisioned for the workspace you intend to approve.
- Step 2: Back up your existing raw MCP configuration before editing it, so you can reverse the change exactly.
- Step 3: Confirm your installed Antigravity build. Client behavior changes between releases, so a menu below can differ in your build.
Add Rivul MCP to Antigravity
- Step 1: Open Agent Settings, Customizations, MCP Servers, then View raw config.
- Step 2: Add Rivul MCP with serverUrl. Do not replace serverUrl with url or httpUrl.
- Step 3: Save the configuration, return to MCP Servers, and choose Authenticate next to Rivul MCP.
{
"mcpServers": {
"rivul-atlas": {
"serverUrl": "https://rivul.ai/mcp"
}
}
}Complete and verify the handoff
- Step 1: When Authenticate opens Rivul, choose the intended workspace and approve the two read-only scopes.
- Step 2: If Rivul displays an authorization code, copy it back into Antigravity and submit it once.
- Step 3: Confirm search_papers and usage_status appear, then run a three-result search and a usage read.
Troubleshooting
Authenticate returns an error or Rivul MCP tools don't appear. Restart Antigravity, check that Rivul MCP is still listed under MCP Servers with serverUrl, and choose Authenticate once more.
Unused grants remain after an interrupted sign-in. Disconnect any temporary Antigravity grant in Rivul MCP and remove the test server entry if it is no longer needed.
You are considering a literal key instead. Antigravity documents custom headers for remote servers, but its guide does not promise environment-variable expansion inside those header values. Never put a real Rivul MCP key in a committed workspace file. A private literal-key configuration is an optional fallback.
Something here wrong or missing? Use the contact form.