This project simplifies the integration of Snowflake stored procedures with an MCP (Model Context Protocol) server. It provides a framework to
This project simplifies the integration of Snowflake stored procedures with an MCP (Model Context Protocol) server. It provides a framework to define, manage, and execute Snowflake procedures from the MCP server environment. That is what the snowflake mcp sp integration mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 2 tools. What each one is for:
Schemas — All store procedures in the specified schemas will be available to the MCP serverProcedures — Only the specified procedures will be available to the MCP serverConfiguration is passed through the environment: SNOWFLAKE_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
uv installedPlenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Snowflake MCP Sp Integration's toolset — Schemas, Procedures — is a fair guide to whether it matches your workflow. It is maintained by Cjaimesg; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Schemas | All store procedures in the specified schemas will be available to the MCP server. |
| Procedures | Only the specified procedures will be available to the MCP server. |
{
"mcpServers": {
"snowflake_sp_server": {
"command": "absolute/path/to/your/uv/uv.exe",
"args": [
"--directory",
"absolute/path/to/snowflake-mcp-sp-integration",
"run",
"main.py",
"--schemas",
"DB_NAME.SCHEMA_NAME",
"--procedures",
"DB_NAME.OTHER_SCHEMA_NAME.PROCEDURE_NAME"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
uv installed| Variable | Description | Required |
|---|---|---|
| SNOWFLAKE_HOST | Endpoint or connection string the server talks to. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.