AutoUncle Data Services is in beta. The API, MCP tools and agent skill may change often, including breaking changes, until version 1.0. Read the changelog before you upgrade an integration.
Gemini & Antigravity
Configure the Data MCP server in Google's Antigravity CLI and IDE, or in the older Gemini CLI.
Note: Google's Gemini CLI documentation states that Gemini CLI was replaced by Antigravity CLI on 18 June 2026. Both are covered here because existing installations still use the Gemini CLI configuration.
Antigravity
Antigravity reads MCP servers from ~/.gemini/config/mcp_config.json (all workspaces) or .agents/mcp_config.json (one workspace). It uses Streamable HTTP with the serverUrl key.
With an API key
{
"mcpServers": {
"autouncle-data": {
"serverUrl": "https://data-services.autouncle.com/mcp",
"headers": { "Authorization": "Bearer au_test_..." }
}
}
}
Antigravity's documentation does not describe environment-variable interpolation in headers, so treat the value as a literal secret: keep it in the global file on your own machine, use a test key, and never commit a workspace file that contains it.
With OAuth
Leave out headers. Antigravity registers itself through dynamic client registration. Open Agent settings → Customizations, choose Authenticate for autouncle-data, sign in with your AutoUncle account, choose the organization and approve the scopes. In the CLI, /mcp opens the server manager. OAuth valuations are live.
Gemini CLI
Gemini CLI reads ~/.gemini/settings.json or a project .gemini/settings.json. Use httpUrl for Streamable HTTP (url means SSE, which this server does not offer).
gemini mcp add --transport http --header "Authorization: Bearer $AUTOUNCLE_API_KEY" autouncle-data https://data-services.autouncle.com/mcp
The shell expands $AUTOUNCLE_API_KEY, so the literal key is stored in the settings file. The resulting entry looks like this:
{
"mcpServers": {
"autouncle-data": {
"httpUrl": "https://data-services.autouncle.com/mcp",
"headers": { "Authorization": "Bearer au_test_..." }
}
}
}
For OAuth, add the server without --header, then run /mcp auth autouncle-data in Gemini CLI to sign in. Gemini CLI discovers the authorization server from the 401 response and registers itself dynamically.
Verify the connection
Ask:
Call get_account on autouncle-data and tell me the key mode, scopes and remaining credits.
Troubleshooting
| Symptom | Fix |
|---|---|
401 invalid_api_key |
The header value is wrong or missing Bearer. |
| Connection fails in Gemini CLI | Use httpUrl, not url. |
| Results are live | You are using OAuth or a live key. Use a test key for free results. |
Sources: Antigravity MCP documentation, Gemini CLI MCP servers.