I use this every day: https://github.com/runekaagaard/mcp-alchemy
I’m sorry, does this send your database to Claude?
Yeah, Claude can query and read the result sets. It does not send the entire database.
Building AI agents to query your databases
51–56 of 56 posts
Re: Building AI agents to query your databases
#52Anyone else wishing their town halls were this sexy?
Re: Building AI agents to query your databases
#53We ( https://www.definite.app/ ) solved this a bit differently. We spin up a data lake and pipelines (we support 500+ integrations / connectors) to populate the data lake for you then put DuckDB on top as a single query engine to access all your data.
Do you host the data lake yourself? How do you handle data privacy?
Some large enterprises won't allow their data to leave e.g. their own Snowflake warehouse. All tooling they use has to run on top of their warehouse.
Re: Building AI agents to query your databases
#54> This abstraction shields users from the complexity of the underlying systems and allows us to add new data sources without changing the user experience. Cursed mission. These sorts of things do work amazingly well for toy problem domains. But, once you get into more complex business involving 4-way+ joins, things go sideways fast. I think it might be possible to have a human in the loop during the SQL authoring pha…
A bit of a joke here: It solves 100% cases where some manager requests dashboard never to look at it again after one day.
> A bit of a joke here:
> It solves 100% cases where some manager requests dashboard never to look at it again after one day.
Better than having engineers build it for days (for the same result).
Re: Building AI agents to query your databases
#55Earlier quoted context omitted.
> It does require writing good instructions for the LLM to properly use the tables --- start quote --- prompt engineering is nothing but an attempt to reverse-engineer a non-deterministic black box for which any of the parameters below are unknown: - training set - weights - constraints on the model - layers between you and the model that transform both your input and the model's output that can change at any time -…
What else is engineering then if not taming the unknown and the unknowable? How is building a bridge any different? Do you know everything in advance about the composition of terrain, the traffic, the wind and the earthquakes? Or are you making educated guesses about unknown quantities to get something that fits into some parameters that are Good Enough(TM) for the given purpose?
> How is building a bridge any different?
In absolutely every way that matters and in all the details that don't matter.
> Do you know everything in advance about the composition of terrain, the traffic, the wind and the earthquakes?
No, and there are established procedures and ways to establish those facts.
"This magical incantation that I pretend works better because the US is asleep and more compute is available" is not such a procedure.
Re: Building AI agents to query your databases
#56AI agents often have access to sensitive or confidential information, and if they are not properly secured or designed with strict access controls, they could inadvertently expose or misuse that data, leading to serious breaches or compliance issues.