A simple configuration file is used to create tooling for the various Cortex AI features. An example can be seen at
MCP Snow Tg MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Snow Tg directly instead of describing what you should do. A simple configuration file is used to create tooling for the various Cortex AI features. An example can be seen at services/service_config.yaml and a template is below. Many Cortex Search and Cortex Analyst.
Once MCP Snow Tg is connected, these are the calls the assistant has available:
service_name — "<service_name>"macOS — ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows — %APPDATA%\Claude\claude_desktop_config.jsonYou will need 3 environment variables: SNOWFLAKE_PAT, SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Snow Tg's toolset — service_name, macOS, Windows — is a fair guide to whether it matches your workflow. It is maintained by sfc-gh-tgordonjr; 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 |
|---|---|
| service_name | "<service_name>" |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
{
"mcpServers": {
"mcp-server-snowflake": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/Snowflake-Labs/mcp",
"mcp-server-snowflake",
"--service-config-file",
"<path to file>/service_config.yaml"
]
"env": {
"SNOWFLAKE_PAT": "<programmatic_access_token>",
"SNOWFLAKE_ACCOUNT": "<account-identifier>",
"SNOWFLAKE_USER": "<username>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SNOWFLAKE_PAT | Configuration value read at startup. | Optional |
| SNOWFLAKE_ACCOUNT | Configuration value read at startup. | Optional |
| SNOWFLAKE_USER | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.