Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | dbtMCP100 Recommended | Codebase Memory MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP ecosystem:dbt · Publisher source ↗ | First-party MCP DeusData · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Sep 24, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 14, 2026 |
| Popularity evidence | ||
| GitHub stars | 610 GitHub stars · checked 2026-09-24T04:14:39.550000Z | 44,904 GitHub stars · checked 2026-09-25T18:35:00Z |
| Package downloads / 30 days | 75,917 package downloads / 30 days · checked 2026-09-24T04:17:50.251000Z | 28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z |
| External adoption evidence | Not documented |
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | The server documents dbt platform credentials and local project configuration. | local stdio; no remote auth needed |
| Cost | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. | none beyond local resources |
| Permissions | dbt platform tokens, project permissions, enabled toolsets, and underlying warehouse roles determine authority. | reads indexed source/project data; installer writes supported agent/editor configs/hooks |
| Data handling | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive analytics & data information. | local processing; current docs state no source/index/query/env/telemetry upload |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Job execution and warehouse-backed queries can change state or incur compute cost. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. | latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy |
| Evidence date | ||
| Editorial review | 2026-07-30 | 2026-09-23 |
| Candidate evidence | 2026-09-24T04:25:05.554391Z | 2026-09-25T18:35:00Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →