← Explore all mcp servers

CONTENT AND DATA MANAGEMENT / Directus

Directus native MCP

Connect directly to a Directus instance for content, schema and workflow operations under its existing permission system.

“Directus MCP”

01 / THE REASONING

Why this made the selection.

  • Built into Directus rather than requiring a separate local adapter for supported versions.
  • Explains default versus registry tool discovery and their approval trade-offs.
  • Directus documents a native MCP server that is disabled until an administrator enables it, and that then uses the connected user’s permissions.
  • OAuth avoids pasting a static token into the client, but the security page says OAuth does not replace scoped permissions.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • https://directus.com/docs/guides/ai/mcp
  • https://directus.com/docs/guides/ai/mcp/installation
  • https://directus.com/docs/guides/ai/mcp/security
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • The installation guide recommends CIMD when available and supports a static-token fallback.
  • Native MCP and the older Node content adapter are alternative paths for one service, not counted separately.
  • The installation page says the Directus MCP server is disabled by default and must be enabled manually. Once enabled, it uses the connected user’s permissions, and tools can only access what that user may see and do.
  • Static tokens are documented for clients that do not support MCP OAuth, preferably on a dedicated user.
  • The security page says OAuth avoids copying a static token into the client, and that OAuth does not remove the need for scoped permissions. The issued token still acts as the approving user.
  • Registry mode exposes a small discovery surface for clients without deferred tool loading; the underlying Directus authentication and permissions still apply.

Not established by this review

  • Server startup, authentication, live tool execution and security isolation were not tested.
  • Published package/container parity with a source revision and hosted implementation internals were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Enable MCP in Settings > AI and select a dedicated user/role.
  2. Configure OAuth and a client registration method supported by the client, or supply a static bearer token privately. Save the user after generating a static token.
  3. Use the default endpoint for per-tool approval; choose registry mode only when its context savings justify the coarser client controls.
  4. Use /mcp?tool_mode=registry only when needed for tool-count/context limits; configure OAuth server plus a supported client-registration method for browser login.

Before you start

  • A reachable Directus 11.12+ instance and compatible authenticated HTTP MCP client.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "directus": {
      "type": "http",
      "url": "https://YOUR_DIRECTUS_HOST/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://directus.com/docs/guides/ai/mcp

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  2. https://directus.com/docs/guides/ai/mcp/installation

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  3. https://directus.com/docs/guides/ai/mcp/security

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

Evidence & Ask