Skip to main content
Glama
Zain-ul-Abdin45

sqlmesh-mcp

by Zain-ul-Abdin45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sqlmesh-mcp

No user-submitted related servers found.

    Related Servers

    • lakehouse-mcp

      The-Vector-007
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect schemas, walk Delta table history, run read-only DuckDB queries, and check data-quality and job-run status safely.
      MIT

    • schema-guard-mcp

      idk-arsh
      A
      license
      A
      quality
      B
      maintenance
      Exposes tools that let AI coding agents browse a repo's schema snapshot of tables and columns and validate their SQL against it before running or writing it, so queries referencing invented or stale table and column names get caught and corrected up front. Provides list_tables, describe_table, search_columns, and check_sql over the same snapshot used by the CLI, hook, and CI check.
      4
      1
      MIT

    • Tilt MCP Server

      aryan-agrawal-glean
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables LLMs and AI assistants to interact with Tilt development environments, providing tools to list resources, fetch logs, and monitor status.
      16,019 PyPI
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    Resources