×

Connect Gemini to your Oracle database

Gemini queries your Oracle data through Myriade's MCP server: with business context, read-only, under each user's access rights.

Prerequisites

• A Myriade account on app.myriade.ai (or on your self-hosted instance).
• Network access from Myriade to Oracle, with a read-only account.
• Gemini, on a plan that allows custom MCP servers (see the note in step 2).

1. Connect Oracle to Myriade

Myriade connects to Oracle with a host, a port (1521 by default) and a service name, or a SID for older databases. The Oracle client ships in the Myriade Docker image: nothing to install. A client-side query timeout can be set per connection.

Best practice: use a dedicated user with CREATE SESSION and SELECT on the useful tables or views only.

2. Add Myriade to Gemini

Gemini reaches remote MCP servers from Gemini CLI, from Gemini Enterprise (added by an admin) and, in the US, from custom apps in the Gemini app.

1. 1Take the Myriade MCP address: https://app.myriade.ai/mcp.
2. 2Add the Myriade server to the Gemini CLI settings.json file (snippet below).
3. 3Start Gemini CLI and run /mcp auth myriade to sign in to Myriade through OAuth.

{ "mcpServers": { "myriade": { "httpUrl": "https://app.myriade.ai/mcp" } } }

Gemini Enterprise: an admin creates a Custom MCP Server data store with this URL in the Google Cloud console. Antigravity CLI, which replaces Gemini CLI on some accounts, uses its own mcp_config.json file (serverUrl key).

Self-hosted Myriade (optional): replace app.myriade.ai with your instance's host.

3. Check the connection

Ask Gemini a few questions:

• “Which tables describe customer orders in Oracle?” The assistant searches the Myriade catalog before writing SQL.
• “What was revenue by region last quarter?” Read-only SQL, run under your access rights, saved in Myriade.
• “Did any alert fire on our KPIs this week?” The assistant reads Myriade's checks and alerts.

What Myriade enforces

• INSERT, UPDATE, DELETE, DROP… blocked; a query that cannot be parsed is rejected
• Maximum duration per query and a cap on concurrent queries
• At most 50 rows returned to the assistant
• Database visibility, team rules on tables and columns
• Protected columns stay masked, including for the assistant

Frequently asked questions