Directus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getItemsC | Get items from a collection in Directus |
| getItemC | Get a single item from a collection by ID |
| createItemC | Create a new item in a collection |
| updateItemC | Update an existing item in a collection |
| deleteItemC | Delete an item from a collection |
| getSystemInfoC | Get system information from Directus |
| getCollectionsC | Get all collection schemas from Directus |
| loginC | Login to Directus and get an access token |
| getActivityC | Get activity logs from Directus |
| getFieldsC | Get fields for a collection |
| getRelationsC | Get relations for a collection |
| getFilesC | Get files from Directus |
| uploadFileC | Upload a file to Directus |
| getUsersC | Get users from Directus |
| getCurrentUserC | Get the current user info |
| getRolesC | Get roles from Directus |
| getPermissionsC | Get permissions from Directus |
| getConfigB | Get current configuration information (without secrets) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Directus ecosystem. There is no overlap between tools like getItem (single item retrieval), getItems (multiple items), and getCollections (schema information), making misselection unlikely.
All tools follow a consistent verb_noun naming pattern (e.g., createItem, getItem, updateItem, deleteItem). The pattern is maintained across all 18 tools with no deviations in style or convention.
With 18 tools, the count is slightly high but reasonable for a comprehensive CMS/backend server like Directus. It covers core operations without being overwhelming, though it borders on the upper limit of ideal scope.
The tool set provides complete CRUD coverage for items (create, get, update, delete), along with essential administrative functions (users, roles, permissions, files, activity, config). No obvious gaps exist for the Directus domain, enabling full agent workflows.