MCP Configuration And Usage In Antigravity¶
Antigravity can use MCP servers to give the assistant controlled access to the same Oracle database used by Cymbal Coffee. For this workshop, keep the setup clean: configure current Antigravity MCP files directly, avoid legacy Gemini CLI migration, and never commit credentials.
Use Oracle SQLcl as the direct MCP bridge for local Oracle SQL operations against the demo schema.
Use Google’s MCP Toolbox Oracle prebuilt profile for database inspection and toolbox-managed SQL execution.
Use the Google Cloud Oracle Database remote MCP endpoint only when teaching the managed Google Cloud MCP flow.
Use least-privilege demo credentials, preview generated config, and keep all secrets outside tracked files.
Config Location¶
Antigravity reads MCP server entries from a user-level mcp_config.json. The
IDE owns a per-app file:
~/.gemini/antigravity/mcp_config.json
On Windows this is %USERPROFILE%\.gemini\antigravity\mcp_config.json. To edit
it without touching the filesystem, open the Agent panel “…” menu, choose
MCP Servers > Manage MCP Servers > View raw config. A shared
~/.gemini/config/mcp_config.json is also read and lets the same entries apply
across Antigravity tools (IDE and CLI); use it when servers should be shared.
Antigravity uses this home-directory model rather than a project-local
.gemini/ config. Keep secret-free examples under .agents/ or docs/, but
the live MCP file belongs in the user’s home directory.
SQLcl MCP¶
SQLcl MCP is the shortest path from Antigravity to the local Oracle 26ai demo
schema. It should use the same app-scoped database user that Cymbal Coffee uses,
not SYS or SYSTEM.
{
"mcpServers": {
"sqlcl": {
"command": "/absolute/path/to/sql",
"args": ["-mcp"]
}
}
}
Use an absolute executable path. Agent and desktop environments often start
without the same PATH as the terminal shell.
MCP Toolbox Oracle¶
Google’s MCP Toolbox can run a prebuilt Oracle server:
{
"mcpServers": {
"oracle-toolbox": {
"command": "/absolute/path/to/toolbox",
"args": ["--prebuilt", "oracledb", "--stdio"],
"env": {
"ORACLE_CONNECTION_STRING": "localhost:1521/FREEPDB1",
"ORACLE_USERNAME": "app",
"ORACLE_PASSWORD": "<set locally>"
}
}
}
}
The prebuilt profile is useful for a workshop because it avoids maintaining a
custom tools.yaml before the teaching flow stabilizes. Move to explicit
Toolbox source configuration later if the lab needs a curated tool list.
Google Cloud Oracle MCP¶
Google Cloud Oracle Database also exposes a remote MCP endpoint:
https://oracledatabase.googleapis.com/mcp
Use this as a separate managed-cloud example. It is a remote HTTP MCP server, so
register it with serverUrl (and auth headers) rather than command/args. It
requires the Oracle Database@Google Cloud API (oracledatabase.googleapis.com)
to be enabled, OAuth 2.0 credentials over IAM (Application Default Credentials
satisfy this), and a principal granted the MCP Tool User role
(roles/mcp.toolUser) plus the resource roles for the databases it touches.
Installer Surface To Add¶
These commands are the intended clean repo interface; they should be added as
explicit installer/configuration actions rather than hidden inside install all:
uv run python manage.py install mcp-toolbox --version 1.5.0
uv run python manage.py install mcp sqlcl --client antigravity --dry-run
uv run python manage.py install mcp oracle-toolbox --client antigravity --dry-run
uv run python manage.py install mcp status
The writer should preserve unrelated MCP servers, replace only repo-owned
entries when requested, and avoid reading legacy ~/.gemini/settings.json.
Visual References¶
Use built-in documentation icons first:
Sphinx Design supports Octicon and Material icon roles for inline SVG icons.
Sphinx Immaterial supports bundled icon names and custom SVG icon paths.
GitHub Octicons are MIT licensed.
Google Material Symbols are Apache-2.0 licensed.
Use official product artwork sparingly:
Google Cloud provides an official icon library for architecture diagrams and technical documentation.
Oracle logo usage is governed by Oracle’s third-party logo and trademark guidelines. Prefer generic database icons in this documentation unless an approved Oracle asset is already part of the project.
Useful references: