Directus Connector for AI agents.

Yes. You can use it to write new records, update existing values, or even wipe records to clear space. It handles the communication with your database so you can just use natural language.

Yes, it works with your PostgreSQL tables. It allows your AI agent to audit your schema, list collections, and manage the data stored within those tables.

You can use it to retrieve structural matches for your media storage. This helps you find file paths and download routes quickly without browsing the CMS.

Yes, you can use it to identify active admin identities and oversee the users authorized within your database layer, helping you manage access more easily.

Yes, you can ask your agent to wipe specific records. This will irreversibly remove them from your database to help manage your data allocations.

Yes. Use the 'list_schema_collections' capability to see all tables, and then use 'list_collection_fields' for a specific collection. The agent retrieves the absolute structural details defining precisely which fields accept formatting.

Use the 'create_cms_record' capability. Provide the collection name and a JSON payload mapping the columns. Your agent will orchestrate the request to drop the formatted endpoint into your database and return the new UUID.

Absolutely. The 'list_directus_users' capability retrieves the explicitly mapped profile arrays iterating the exact users authorized within the database layer. This helps you monitor RBAC boundaries and organizational identities.

Yes! Use create_item with a collection name and JSON payload to add new items. Use update_item with the collection, item ID, and updated fields to modify existing items. Use delete_item to remove items. All operations respect the permissions assigned to your Static Token's user role.

Directus uses a non-expiring Static Token associated with a specific user account. Generate it from your User Profile in the Data Studio. The token is sent as a Bearer token in the Authorization header. Its permissions match the role assigned to that user. use an admin role for full access or a restricted role for read-only operations.

Yes. The list_activity capability retrieves the audit log of recent database operations, showing who made changes, which collections were affected, timestamps, and the type of operation (create, update, delete). Combine with list_users and list_roles for full accountability tracking.