---
title: "Directus native MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/directus-native/
description: "Connect directly to a Directus instance for content, schema and workflow operations under its existing permission system."
---

# Directus native MCP: review, setup & limitations · Undominated.ai

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

[← Explore all mcp servers](/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.

 [See setup guidance ↓](#setup)[Original source ↗](https://directus.com/docs/guides/ai/mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Directus
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Directus MCP”

 [Directus · upstream description ↗](https://directus.com/docs/guides/ai/mcp) Our analysis follows below.

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.

### A good fit for

 - Inspect collections and draft a content update using a dedicated restricted user.
- Prototype relationships and workflows in a development instance.
- Letting an AI tool manage a Directus instance as a dedicated user with a narrow role
- A client that cannot do MCP OAuth, using a static token for that same dedicated user

### Weigh up before choosing

 - MCP is disabled by default; native support requires Directus 11.12+.
- Registry mode routes inner operations through execute, preventing individual client approval rules for those inner tools.
- Keep Allow Deletes disabled unless needed; it does not prohibit other writes.
- The server is disabled by default. Enabling it does not create a permission above the connected user.
- OAuth does not remove the need for scoped permissions.
- No licence was stated on these pages, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Registry mode changes tool discovery rather than user authority. A client already doing tool search generally does not need a second discovery layer.

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 ↗](https://directus.com/docs/guides/ai/mcp)
 - Enable MCP in Settings > AI and select a dedicated user/role.
- 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.
- Use the default endpoint for per-tool approval; choose registry mode only when its context savings justify the coarser client controls.
- 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"
 }
 }
} Copy configuration ↗

### Compatibility

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

### Transports

Streamable HTTP

### Content and data management

 - Existing user permissions govern content, schema and workflow access.
- Registry discovery does not grant broader Directus permissions.

### Cost model

Directus hosting/licensing and external model usage apply; no standalone native-server redistribution grant was established.

04 / FOLLOW THE EVIDENCE

## The source trail.

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

 - [Publisher setup, capabilities and operating boundaries ↗](https://directus.com/docs/guides/ai/mcp) Checked 2026-10-14 https://directus.com/docs/guides/ai/mcp Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Publisher setup, capabilities and operating boundaries ↗](https://directus.com/docs/guides/ai/mcp/installation) Checked 2026-10-14 https://directus.com/docs/guides/ai/mcp/installation Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Publisher setup, capabilities and operating boundaries ↗](https://directus.com/docs/guides/ai/mcp/security) Checked 2026-10-14 https://directus.com/docs/guides/ai/mcp/security Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
