Connect Gemini to your Snowflake database
Gemini queries your Snowflake data through Myriade's MCP server: with business context, read-only, under each user's access rights.
Standard MCP · not tested by MyriadePrerequisites
- A Myriade account on app.myriade.ai (or on your self-hosted instance).
- Network access from Myriade to Snowflake, with a read-only account.
- Gemini, on a plan that allows custom MCP servers (see the note in step 2).
1. Connect Snowflake to Myriade
Myriade connects to your Snowflake account and supports key-pair authentication, with an encrypted key or not. A client-side query timeout can be set per connection.
Best practice: use a dedicated role with USAGE on the warehouse, database and schemas, and SELECT on the tables.
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.
- 1Take the Myriade MCP address: https://app.myriade.ai/mcp.
- 2Add the Myriade server to the Gemini CLI settings.json file (snippet below).
- 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 Snowflake?” 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
Can Gemini modify or delete data in Snowflake?
No. SQL queries that Gemini sends through Myriade's MCP server are parsed before they reach Snowflake: any write (INSERT, UPDATE, DELETE, DROP…) is rejected, even nested in a subquery, and a query that cannot be parsed is refused. As a precaution, also connect Myriade to Snowflake with a read-only account.
Does Gemini connect directly to Snowflake?
No. Gemini only talks to Myriade's MCP server: Myriade alone holds the Snowflake credentials and runs the queries. On Myriade Cloud, the MCP address is public and Myriade must be able to reach Snowflake. If you choose to self-host Myriade, the connection to Snowflake starts from your own infrastructure, and the MCP address must stay reachable by Gemini.
Is Gemini compatible with Myriade?
Gemini supports remote MCP servers, and Myriade exposes a standard MCP server (Streamable HTTP, OAuth). Myriade has not tested this connection yet: tell us if you try it, we will help you set it up.
No Myriade account yet?
Book a demo to see Myriade on your own data.
