Directus Content MCP Server

The Directus Content MCP Server connects an MCP client to a Directus instance so that the people who actually work in the CMS — editors assembling pages, analysts pulling numbers out of collections — can do it in conversation rather than through the admin UI.

What it exposes

Twenty-odd tools, grouped roughly as:

• Schema and discovery — read the collections schema and field definitions so the model knows what your data model looks like before it queries it.
• Items — read, create, update and delete items in a collection, with Directus's normal filter and field-selection semantics.
• Files — fetch file metadata and manage assets, which is the piece that makes "build me this page" workflows practical.
• Flows — trigger Directus Flows, so an agent can hand off to automation you have already built.
• Comments — read and write item comments, keeping an editorial trail in the same place the team already looks.
• Prompts — a configurable system prompt plus custom prompt templates stored in a Directus collection, with mustache templating, so an organisation can ship its own house instructions alongside the data.
• Utility — markdown conversion and current-user lookup.

Deliberate guardrails

The genuinely destructive schema operations — deleting fields, deleting collections — are intentionally left out. The server can churn content but cannot quietly demolish the data model behind it. DISABLE_TOOLS narrows the surface further if you want a read-mostly deployment.

Setup

Runs straight from npm: npx @directus/content-mcp@latest. Authenticate with DIRECTUS_URL plus either a static DIRECTUS_TOKEN or DIRECTUS_USER_EMAIL and DIRECTUS_USER_PASSWORD. Because Directus applies its own role and permission model to whatever credential you supply, the cleanest setup is a dedicated role scoped to exactly the collections the agent should see. MIT licensed.