MCP server that routes SQL queries through the Greybeam proxy while delegating Cortex Search to upstream Snowflake MCP.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"greybeam-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Greybeam MCP A single MCP server that lets agents query data through the Greybeam routing layer with Snowflake-compatible tooling. - `run_snowflake_query` — executes SQL via the Greybeam proxy (Snowflake protocol). - `cortex_analyst` — calls Snowflake Cortex Analyst; any returned SQL is executed via Greybeam. - `cortex_search` — delegated to the pinned upstream Snowflake MCP (no SQL, REST only). Out of scope for v1: Cortex Agent, semantic views, and the upstream `object_manager` / `query_manager` / `semantic_manager` tool families. These are locked off in the child config so a misconfigured deployment can't accidentally expose them. ## Quick start Install and run the setup wizard with [`uv`](https://docs.astral.sh/uv/): uvx greybeam-mcp init The `init` wizard prompts for account, user, proxy host, and auth method; writes a config file at `~/.config/greybeam-mcp.yaml` (mode 0600); and prints the exact registration command for Claude Code and Claude Desktop. For a packaged install, the printed command uses this form: claude mcp add greybeam -- uvx greybeam-mcp --config ~/.config/greybeam-mcp.yaml ## Manual install and run If you'd rather author the YAML by hand, copy `examples/greybeam.yaml` to a location of your choice, edit it, `chmod 600` it, then: uvx greybeam-mcp --config /absolute/path/to/greybeam.yaml From a source checkout, use `uv run` instead: uv run greybeam-mcp --config /absolute/path/to/greybeam.yaml ## Configuration The YAML is the single source of truth — it holds account, proxy host, **and** auth credentials. Pick one auth method (in order of recommendation): - `private_key_file` (path to a PEM key, plus optional `private_key_passphrase`) — **recommended**, since Snowflake is deprecating password auth - `private_key` (inline PEM contents) — for environments without a writable disk - `authenticator: externalbrowser` for SSO (requires a SAML2 integration on the account) - `password` — deprecated by Snowflake, avoid for…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.