Snowflake (official)

Snowflake (official)

Official

Snowflake-managed MCP servers — Cortex Analyst, Cortex Search, and gated SQL, with RBAC and masking enforced by Snowflake.

Score 55(?)SnowflakeProprietaryVerified Top MCPs for Databases

Quick answer

What it does

Serves a named set of Snowflake tools over an authenticated HTTP endpoint hosted by Snowflake. The server object's YAML specification decides which of the five tool types are exposed and against which objects; every call is then subject to the caller's role, row-access policies, and masking policies.

Best for

  • Cortex Analyst natural-language querying
  • Cortex Search over unstructured data
  • Governed agent access with RBAC and masking
  • Publishing UDFs and stored procedures as agent tools

Not for

  • Developers without CREATE MCP SERVER privilege
  • Government-region accounts

Source: top-mcps.com/mcp/snowflake-mcp-server — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "snowflake-mcp-server": {
          "command": "CREATE",
          "args": [
            "MCP",
            "SERVER",
            "<name>",
            "FROM",
            "SPECIFICATION",
            "$$",
            "…",
            "$$;",
            "then",
            "point",
            "your",
            "client",
            "at",
            "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
          ]
        }
      }
    }

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    claude mcp add snowflake-mcp-server -- CREATE MCP SERVER <name> FROM SPECIFICATION $$ … $$; then point your client at https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
      "mcpServers": {
        "snowflake-mcp-server": {
          "command": "CREATE",
          "args": [
            "MCP",
            "SERVER",
            "<name>",
            "FROM",
            "SPECIFICATION",
            "$$",
            "…",
            "$$;",
            "then",
            "point",
            "your",
            "client",
            "at",
            "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
          ]
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
      "servers": {
        "snowflake-mcp-server": {
          "command": "CREATE",
          "args": [
            "MCP",
            "SERVER",
            "<name>",
            "FROM",
            "SPECIFICATION",
            "$$",
            "…",
            "$$;",
            "then",
            "point",
            "your",
            "client",
            "at",
            "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
          ]
        }
      }
    }

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "snowflake-mcp-server": {
          "command": "CREATE",
          "args": [
            "MCP",
            "SERVER",
            "<name>",
            "FROM",
            "SPECIFICATION",
            "$$",
            "…",
            "$$;",
            "then",
            "point",
            "your",
            "client",
            "at",
            "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
          ]
        }
      }
    }

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "snowflake-mcp-server": {
          "command": "CREATE",
          "args": [
            "MCP",
            "SERVER",
            "<name>",
            "FROM",
            "SPECIFICATION",
            "$$",
            "…",
            "$$;",
            "then",
            "point",
            "your",
            "client",
            "at",
            "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
          ]
        }
      }
    }

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "stdio",
              "command": "CREATE",
              "args": [
                "MCP",
                "SERVER",
                "<name>",
                "FROM",
                "SPECIFICATION",
                "$$",
                "…",
                "$$;",
                "then",
                "point",
                "your",
                "client",
                "at",
                "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
              ]
            }
          }
        ]
      }
    }

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
    [mcp_servers.snowflake-mcp-server]
    command = "CREATE"
    args = [
      "MCP",
      "SERVER",
      "<name>",
      "FROM",
      "SPECIFICATION",
      "$$",
      "…",
      "$$;",
      "then",
      "point",
      "your",
      "client",
      "at",
      "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>",
    ]

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "snowflake-mcp-server": {
          "command": {
            "path": "CREATE",
            "args": [
              "MCP",
              "SERVER",
              "<name>",
              "FROM",
              "SPECIFICATION",
              "$$",
              "…",
              "$$;",
              "then",
              "point",
              "your",
              "client",
              "at",
              "https://<account_url>/api/v2/databases/<db>/schemas/<schema>/mcp-servers/<name>"
            ]
          }
        }
      }
    }

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Snowflake (official) doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Read + write
Sandbox
Hosted by Snowflake inside the account. Authorisation is Snowflake OAuth (or a programmatic access token) resolving to a real Snowflake role, so every tool call is evaluated against that role's privileges, row-access policies, and masking policies. No credentials leave the account and no local process runs.
Gotchas
  • SYSTEM_EXECUTE_SQL exposes arbitrary SQL under the caller's role — include it only when the roles that can reach the server are ones you would hand a SQL console.
  • A GENERIC tool runs your own UDF or stored procedure, so its blast radius is whatever that procedure does, not what the MCP layer allows.
  • MCP server objects are not replicated in failover groups; a failover leaves agents pointing at an endpoint that no longer exists.
  • Responses from SQL and generic tools are truncated at 250 KB, so a broad query returns a silently partial answer rather than an error.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. databases work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-databases
Compare Snowflake (official) against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Snowflake (official) MCP vs [Snowflake (community) MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/snowflake-mcp-server
- top-mcps.com listing for Snowflake (community)
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Snowflake (official) MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/snowflake-mcp-server (fetch https://top-mcps.com/mcp/snowflake-mcp-server.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Databases MCPs

Other tools in the same category worth evaluating.

Postgres MCP ProPRO

Production-grade Postgres MCP with index advice, EXPLAIN, and health checks.

database, sql, postgres, performance
5 minMedium
SQLite

Local SQLite database access with full read/write support.

database, sqlite, local, storage
2 minLow

Full Supabase access: database, auth, storage, and edge functions.

supabase, database, backend, postgres
5 minLow

Compared with Snowflake (official)

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Databases? See all Databases MCPs →