← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionDirectus Content MCP ServerLet LLMs interact directly with your Directus data.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS70 / 100 · B74 / 100 · B
Reliability10 / 2013 / 20
Security and permissions15 / 2013 / 20
Maintenance12 / 2016 / 20
Documentation18 / 2015 / 20
Setup experience15 / 2017 / 20
Best for
  • Content teams already on Directus who want to read and write content via LLMs
  • Analysts querying Directus data with natural language
  • Directus projects wanting controlled, guardrailed data access for non-developers
  • 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
  • Projects not using Directus
  • Developers needing full destructive/admin operations on dev instances (field and collection deletion is intentionally limited)
  • Clients that do not support MCP
  • 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
  • Requires the Directus instance URL plus a static token or email/password credentials
  • Actions are limited by the permissions of the associated Directus user
  • 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
  • Has write access to create, update, and delete items and fields, so misconfiguration can still modify data
  • Leaked credentials grant LLM access to Directus data
  • While field/collection deletion is limited, item deletion remains available
  • 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 Desktop, CursorClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools212