Anything can call createItem. Knowing which fields exist, which are required, and what a relation points at is the part that decides whether the call succeeds — and getCollections, getFields and getRelations are here for exactly that. Two auth paths is a genuine convenience: a static token for an unattended setup, email and password when you want the session to carry your own permissions.
A server over the Directus REST API. It covers the content operations plus enough of the schema and access surfaces that an assistant can understand a collection before editing anything in it.
- getItems, getItem, createItem, updateItem and deleteItem cover content in any collection
- getCollections returns all collection schemas; getFields and getRelations explain a collection's shape and how it links to others
- getFiles and uploadFile handle the file library
- login, getUsers, getCurrentUser, getRoles and getPermissions cover identity and access
- getSystemInfo, getActivity and getConfig answer questions about the instance itself and what has been happening in it
- Switching MCP_TRANSPORT to http serves Streamable HTTP at /mcp for multi-user or remote setups, with MCP_PORT and MCP_HOST controlling the binding
Node.js and npm, plus a Directus instance. Authenticate either with DIRECTUS_URL and DIRECTUS_ACCESS_TOKEN — a static token created in Directus — or with DIRECTUS_URL, DIRECTUS_EMAIL and DIRECTUS_PASSWORD. Runs over npx for stdio; a container image at ghcr.io/pixelsock/directus-mcp covers the HTTP path.