| name | directus-mcp-connector |
| description | MCP connector for Directus data platform – enables AI-powered data modeling, content management, and workflow automation through Claude |
| license | GPL |
| tags | ["dev","cms","mcp","directus","api"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Directus MCP Connector
Overview
This skill enables Claude to interact with Directus through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Directus's REST/GraphQL, allowing natural language control of Directus operations, intelligent automation, and AI-powered assistance for Directus workflows.
When to Use This Skill
- Collection and field design via AI
- Flow and automation creation
- Dashboard widget configuration
- Role-based access control setup
- Data import/export and transformation
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Directus │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST/GraphQL )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Directus operations as tools Claude can invoke. The server translates natural language intentions into REST/GraphQL calls.
Key Endpoints/Interfaces
/items/:collection, /collections, /fields, /flows, /dashboards
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "directus-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Directus resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/items/:collection`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"directus-mcp-connector": {
"command": "node",
"args": ["path/to/directus-mcp-connector/index.js"],
"env": {
"DIRECTUS_API_KEY": "your-api-key",
"DIRECTUS_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Directus API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Directus API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a collection for Blog Posts with a review workflow that sends notifications on publish"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.