Bauplan MCP Server
OfficialRelated Servers
Alternatives to Bauplan MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to execute SQL, explore schemas, retrieve internal metrics, generate Plotly charts, and obtain table/database overviews from a connected data warehouse.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to execute SQL, explore database schemas and sample data, inspect system metrics, and generate Plotly charts from query results.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to explore Unity Catalog metadata, execute SQL queries, and analyze data lineage including notebooks and jobs, empowering autonomous data discovery and query generation in Databricks.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform comprehensive Snowflake database operations including DDL, DML, and warehouse management. It allows users to query data, manage database objects, and configure permissions using natural language commands.MIT
- AlicenseBqualityBmaintenanceEnables LLM agents to interact with a SQLMesh project, providing model metadata, column-level lineage, plan previews, audits/tests, and environment diffs, with optional apply/run actions.271MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to directly execute SQL, explore schemas and system metrics, retrieve table and database overviews, and generate Plotly charts from query results.-
TDQS
Scored across 33 tools
Most tools have clearly distinct purposes (e.g., create, get, delete for different resources). Potential overlaps like code_run vs project_run and run_query vs run_query_to_csv are mitigated by detailed descriptions. A few pairs could still cause confusion, but overall boundaries are clear.
Naming patterns are mixed: some use verb_noun (create_branch), others verb_noun_noun (apply_table_creation_plan), and retrieval uses both 'get_' and 'list_' inconsistently (e.g., get_branches vs list_tables). While still readable, the inconsistency may hinder quick tool selection.
With 33 tools, the server is on the heavier side for a typical MCP server. While the domain (data catalog and pipelines) justifies many operations, some tools like multiple query variants and plan phases could be consolidated. Not extreme, but above ideal.
The tool surface covers CRUD for branches, namespaces, tables, and tags, plus job management, query execution, and pipeline runs. Missing explicit update tools (e.g., update_table) but those are handled via merge/revert/import. The inclusion of a meta-instruction tool is helpful. Minor gaps exist but overall solid.