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
An officially maintained MCP server for Directus data with comprehensive tool coverage (items, files, fields, flows, comments, prompts), built-in guardrails against data loss, and solid config options. Ideal for content and analysis workflows; useless outside Directus, and intentionally restrictive for developers needing destructive operations.
The Directus Content MCP Server is the official MCP interface for Directus users to interact with their data in LLMs. Content editors can build pages, write blog posts, and organize assets, while data analysts can query collections, generate reports, and extract insights using natural language. It intentionally limits destructive actions like deleting fields or collections, and supports system prompts, dynamic prompts stored in Directus collections, Mustache templating, and tool restrictions via DISABLE_TOOLS.
Prerequisite: an existing Directus project (free trial on Directus Cloud, or run npx directus-template-cli@latest init locally). Step 1: get credentials — generate a static token in your user profile (remember to save the user) or use email and password. Step 2: add the server to Claude Desktop or Cursor MCP config with command npx @directus/content-mcp@latest and env vars DIRECTUS_URL plus DIRECTUS_TOKEN (or DIRECTUS_USER_EMAIL / DIRECTUS_USER_PASSWORD), save and restart the client. Local dev: clone the repo, run pnpm install && pnpm build, point the config at dist/index.js, and use pnpm dev to watch changes.
{"mcpServers":{"directus":{"command":"npx","args":["@directus/content-mcp@latest"],"env":{"DIRECTUS_URL":"https://your-directus-url.com","DIRECTUS_TOKEN":"your-directus-token"}}}}