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

    • Langfuse MCP Server

      NicolasPastore3399
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and developers to query traces, sessions, and exceptions for debugging and observability, alongside tools for prompts, datasets, annotation queues, scores, and metrics. Supports selective tool loading and a read-only mode for safer local access from any MCP client.
      -

    • 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
    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

    B3.3/5.0

    Scored across 27 tools

    Disambiguation3/5

    Several tools have overlapping intent: plan vs start_plan and run vs start_run are synchronous/async variants of the same operation, while get_model_dependencies, model_impact, and lineage all cover dependency graphs, and plan/diff_environment/table_diff all compare state. The detailed descriptions do explicitly explain the distinctions, so an agent can disambiguate, but the sync/async pairs and parallel comparison tools invite misselection.

    Naming Consistency3/5

    All names are snake_case, which is consistent, but verb convention is mixed: verb_noun (get_model, run_audit, apply_plan), reversed noun_verb (table_diff vs diff_environment), and bare nouns (lineage, model_impact, server_info, environment_health) coexist. It remains readable but does not follow a single predictable pattern.

    Tool Count3/5

    27 tools is above the comfortable range and is inflated by dual synchronous/asynchronous variants (plan/start_plan, run/start_run plus job status/cancel) and conditional tools (register/approve_cleansing_plan only matter when approval is enabled). Still, the SQLMesh domain is genuinely broad (models, plans, runs, jobs, audits, tests, environments, cleansing), so most tools earn their place.

    Completeness4/5

    The surface covers the domain thoroughly: model inspection/lineage, plan preview+apply, scheduled runs, job lifecycle, audits/tests, environment diff/health, formatting, and a full cleansing lifecycle. Minor gaps exist (no job listing, no model create/edit since models live as files), but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources