Can AI agents automate Directus?

Directus is automatable today through the APIs it generates from a connected database. REST item endpoints such as GET and POST /items/posts accept Authorization Bearer with a static access token. The authentication guide also documents a session cookie named directus_session_token and an access_token query parameter, and it says to prefer a method other than the query parameter. The homepage says Directus generates REST and GraphQL APIs. The docs show a JavaScript client, @directus/sdk. Directus v11.12 or later includes a remote MCP server at /mcp. It is disabled until an administrator enables it under Settings, AI, Model Context Protocol. Auth is OAuth or a static user token. Registry mode at /mcp?tool_mode=registry exposes search, execute, and schema. Deletes stay off unless Allow Deletes is enabled. Permissions follow the connected user. Directus is licensed under the Monospace Sustainable Core License. A self-hosted instance without a license runs on the core tier. Higher limits need a paid license. If an instance is over its entitlement and the grace period has elapsed, item, GraphQL, and MCP APIs are disabled. The homepage says the same product can be self-hosted or run on Directus Cloud, and self-hosting can start free. Zapier, Make, Power Automate, and n8n were not assessed. A command-line inventory was not established. Computer-use viability is unassessed. API scores 8. MCP scores 7. API is the best path because a static bearer token calls generated item endpoints directly, without enabling MCP.

Best path today: api · Overall automatability: 8/10