This looks really cool, but I'm struggling to understand why I might want to use it. Right now I'm able to query databases from Cloud Code. Is this a way that it can dynamically understand and explore the schema so I don't have to preload a schema file like I currently do?
Our MCP server does understand how to explore and understand the database schema, and if the knowledgebase package is installed (which you can install from our Enterprise repos, or build one yourself with whatever content you like), it has semantic search capabilities over all the PostgreSQL, pgAdmin, PostGIS, pgEdge and other docs so it has a full understanding of the database and technologies used in it, even if the chosen LLM hasn't been trained on them or only has partial training on them. It can even perform semantic searches over any data you might have embeddings for in the database, provided you configure it to use the correctly embedding LLM, allowing arbitrary semantic searches of content in databases of which it has no prior schema knowledge.
Ours is the only MCP server for Postgres that is fully featured, fully supported by an actual Postgres company AND works with any existing Postgres database on any standard version of Postgres from v14 on.
Note that the MCP server is far better optimised than using psql; it uses lots of tricks to manage token budget, and has tools specifically designed to make database interaction easier, faster, and more efficient.
