MCP Server for Interacting with Cube Semantic Layers
Snowflake Cube Server MCP server exists for a simple reason — assistants are far more useful when they can act on Snowflake Cube Server directly instead of describing what you should do. MCP Server for Interacting with Cube Semantic Layers.
MCP Server for Interacting with Cube Semantic Layers
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Once Snowflake Cube Server is connected, these are the calls the assistant has available:
read_data — Accepts a query to the Cube REST API and returns the data in YAML along with a unique identifier for the data returned. This identifier can be useddescribe_data — Describes the data available in the Cube deployment. This is an agentic version of the context://data_description resourceAmong the database access 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. Snowflake Cube Server's toolset — read_data, describe_data — is a fair guide to whether it matches your workflow. It is maintained by isaacwasserman; 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 |
|---|---|
| read_data | Accepts a query to the Cube REST API and returns the data in YAML along with a unique identifier for the data returned. This identifier can be used to a retrieve a JSON representation of the data from the resource data:/ |
| describe_data | Describes the data available in the Cube deployment. This is an agentic version of the context://data_description resource. |
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.