Basedash MCP server - Your data analyst, in every AI tool you already use
by•
Basedash is now an MCP server. Connect Claude, Cursor, ChatGPT, or any MCP-compatible client and your AI agent can ask Basedash anything about your data — across every database, warehouse, and SaaS tool you've already connected to your workspace. It can pull live numbers, compare cohorts, generate charts, and dig into trends, all governed by the same access controls your team already uses. Your data analyst, inside every tool you ship in.


Replies
Basedash
Hookdeck
Love @Basedash. The MCP could be a game changer for some of my Claude cowork workflows 🙌
@maxmusing flipping the integration direction is the right call. Every other BI tool asks agents to come to the data — this makes the data go to where the agent already is. The permissions-inheritance model is the part I'd bet on: agents querying live numbers inside the same access controls your team trusts removes the "shadow analytics" problem. How are you handling schema discovery for databases with hundreds of tables — does the MCP expose a search/filter layer or does the agent get the full schema dump?
Flipping the model so Basedash plugs into your AI tools instead of the other way around is great because that's where the queries actually happen. I'm curious to know if the MCP server handle ambiguous questions where the answer depends on how a metric is defined, or if it surface the raw data and let the LLM interpret.
very fascinated by the fact that we can now integrate a BI model into any mcp- compatible tool. I am very interested to know more about the administrative side of things or more like if a company could control what rows/columns a user can access as there can be many attributes containing sensitive info that the company would not like for the users to see.
The mcp server is the right call , bringing data to the agent instead of building another dashboard humans have to open. quick question: if i connect two separate postgres instances, can it join across both in a single prompt or does schema discovery stay siloed per connection?