M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

Dimensiondbt MCP ServerAn MCP server for interacting with dbt.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS65 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance16 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Data teams using dbt Core, dbt Fusion, or dbt Platform.
  • Developers looking to integrate AI assistance into data workflows.
  • Analysts needing to quickly explore and understand dbt project structure and lineage.
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users without a dbt project or without plans to use dbt.
  • A general-purpose database MCP server for comprehensive database management.
  • Newcomers unaware of the risks of executing dbt commands like run or build.
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Execute SQL queries (which may modify data).
  • Run dbt commands (e.g., run, build, test), which can modify data models, sources, and warehouse objects.
  • Access dbt Platform APIs such as Discovery API and Admin API.
  • Access local file system (e.g., manifest.json) for local tools.
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Running dbt CLI commands can cause significant modifications to data models, sources, and warehouse objects, potentially leading to data loss or corruption.
  • Executing SQL queries may have unintended side effects, especially in production environments.
  • Access to sensitive data (e.g., job configurations, query results) requires proper authentication and authorization.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools610