Bauplan MCP Serverofficial
A
licenseB
qualityB
maintenanceEnables AI assistants to interact with Bauplan lakehouse operations, including querying tables, schema inspection, branch management, and pipeline execution.
33
15
MIT
sqlmesh-mcp
Related Servers
Alternatives to sqlmesh-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables LLMs and AI assistants to interact with Tilt development environments, providing tools to list resources, fetch logs, and monitor status.18,555 PyPI4MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Hopsworks for platform management, feature store operations, model lifecycle, jobs, and integrations.-
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with DBT (Data Build Tool) projects, allowing them to query project metadata, inspect models and sources, view compiled SQL, and run DBT commands.1415MIT
- AlicenseBqualityDmaintenanceEnables AI agents to interact with Dagster instances, explore data pipelines, monitor runs, and manage assets.924Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to develop within a local project workspace by reading and modifying files, running commands and tests, checking Git state, and persisting progress as history sessions that can be restored in later conversations.-
TDQS
A3.9/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct action or resource: list/get separate models, plan/apply_plan are explicitly linked via plan_id, and run_audit/run_test/diff_environment/list_environments have clear boundaries. The plan/apply_plan and run descriptions explicitly prevent confusion between planning, applying, and executing scheduled runs.
Naming Consistency4/5
Most tools follow a clean verb_noun pattern (list_models, get_model, apply_plan, run_audit, run_test, diff_environment, list_environments). Minor deviations exist with bare verbs like 'plan' and 'run' and noun-only 'lineage', but the naming remains predictable and readable overall.
Tool Count5/5
Ten tools is well-scoped for a SQLMesh project server, covering model inspection, environment planning, execution, testing, auditing, and lineage. Each tool has a clear purpose and none feel redundant or excessive.
Completeness4/5
The core SQLMesh workflow is covered: model inspection, plan preview/apply, environment listing/diffing, audits, tests, and scheduled runs. Missing explicit environment create/delete and model editing are minor because plan/apply and external file workflows can cover those needs, but there are no severe dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues