Skip to main content
Glama
Skeyelab

Directus MCP Server

by Skeyelab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Directus MCP Server

No user-submitted related servers found.

    Related Servers

    • Directus MCP Server

      staminna
      A
      license
      B
      quality
      B
      maintenance
      Enables comprehensive interaction with Directus CMS including collection management, file operations, flow automation, user management, and schema analysis through natural language commands.
      34
      76 npm
      MIT

    • Strapi MCP Server

      andychoi
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI agents with full access to Strapi 5.x CMS for managing content types, entries, media, and schemas. It supports full CRUD operations, relation management, and secure authentication for comprehensive content administration.
      -
    • Directus Content MCP Server by directus

      Directus Content MCP Serverofficial

      directus
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Directus users to interact with their data in LLMs, allowing content editors and data analysts to manage content, query collections, and perform data operations using natural language.
      140 npm
      84
      MIT

    • Directus MCP Server

      JoshTheDerf
      A
      license
      Not graded
      quality
      D
      maintenance
      An extension that implements the Model Context Protocol for Directus, enabling AI tools and LLMs to interact with Directus content through natural language for content editing, data analysis, and asset management.
      4 npm
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a distinct purpose: create vs update vs delete for different resources (collections, fields, items, relations), plus bulk variants and querying. No overlap that could confuse an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., create_collection, list_fields, bulk_create_items). Prefixes like bulk_ are applied uniformly. No mixing of conventions.

    Tool Count4/5

    20 tools cover the core operations of a headless CMS: CRUD for collections, fields, items, relations, plus bulk and query. Slightly on the high side but still well-scoped for the domain.

    Completeness4/5

    Covers CRUD for all main entities plus bulk operations and advanced querying. Minor gaps: no explicit list_items (query_items serves that role), no update for relations, and missing some higher-level features like user management, but core data operations are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources