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.

DimensionSLayerAn embeddable, expressive semantic layer for AI agents and humansDBHubBytebase's official, minimalist two-tool database MCP server
FMRS48 / 100 · D74 / 100 · B
Reliability7 / 2013 / 20
Security and permissions9 / 2013 / 20
Maintenance10 / 2016 / 20
Documentation10 / 2015 / 20
Setup experience12 / 2017 / 20
Best for
  • Data teams wanting a governed data access surface for AI agents
  • Developers building analytical MCP servers or APIs on top of a warehouse
  • Teams with existing dbt, Cube, or Ossie semantic configs they want to reuse
  • Engineers embedding a semantic layer into Python apps
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
Not for
  • Scenarios requiring write access to the database (SLayer connections are read-only)
  • Simple cases where direct SQL is sufficient and no semantic layer is needed
  • Non-Python stacks that cannot run the CLI or an MCP subprocess
  • Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
Required permissions
  • Read-only database access to configured datasources
  • Environment variables holding database credentials such as DB_PASSWORD
  • Permission to run the local CLI and the MCP subprocess
  • Permission to modify Claude Code MCP configuration
  • Requires a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
Risks and side effects
  • Database credentials are passed to the MCP subprocess via environment variables, so a compromised launching shell could expose them
  • Connections are read-only but can still read sensitive business data, so row-level security should be applied
  • Once connected via MCP, agents can run queries, so verify their query scope matches expectations
  • As a third-party project, availability and behavior depend on upstream maintenance
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude CodeClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools02