devkit for strapi mcp changelog

version

0.2.4 → 0.2.5

website_url

https://devkit-for-strapi.paulrichez.fr/mcp/ → https://devkit-for-strapi.paulrichez.fr/mcp/?utm_source=mcp-registry&utm_medium=homepage

version

0.2.2 → 0.2.4

https://devkit-for-strapi.paulrichez.fr/llms.txt

− - [MCP tool reference](https://devkit-for-strapi.paulrichez.fr/mcp-tools/): all 31 tools with parameters — server_info, add_project, project selection (from/project), the read/analyse tools, and the plan → review → apply refactor contract.− The MCP server exposes the project's real values to AI agents so they stop hallucinating magic strings. Unlike content/runtime Strapi MCP servers (which CRUD the entries of a *running* instance via an admin token), DevKit's MCP is **static code analysis**: it reads your `schema.json` from disk and answers about the *codebase* — UIDs, references, dead code, refactors — with no running Strapi instance. Use it when the goal is correct code (a controller calling `strapi.service('api::x.x')`), not co− - Read & analyse (free): `server_info` (running version, licence tier, which tools actually run), `add_project`, `list_projects`, `list_content_types`, `list_components`, `list_artifacts`, `get_schema`, `resolve`, `validate_reference`, `find_references`, `list_routes`, `list_unused`, `list_broken_refs`, `coverage`, `find_relation_usages`, `list_refs`, `dependencies`, `dependents`, `refresh` (re-scan after out-of-band edits).+ Installed plugins are verified too: DevKit reads the plugins in `node_modules` (internal ones, plugin dependencies, honouring `config/plugins`) statically, without executing them, so `plugin::users-permissions.usr` or `strapi::corss` get a "did you mean". A plugin it cannot read completely stays unverifiable (`external`). The editor also has a **Strapi Routes** view, and the MCP `list_routes` tool returns every route with its mounted path, handler, `auth: false` flag and declaration location, pl+ - [MCP tool reference](https://devkit-for-strapi.paulrichez.fr/mcp-tools/): all 37 tools with parameters — server_info, add_project, project selection (from/project), the read/analyse tools (list_routes with a route's pipeline in Strapi's order), the data-model diagram as Mermaid, and the plan → review → apply refactor contract.+ The MCP server exposes the project's real values to AI agents so they stop hallucinating magic strings. Unlike content/runtime Strapi MCP servers (which CRUD the entries of a *running* instance via an admin token), DevKit's MCP is **static code analysis**: it reads your `schema.json` from disk and answers about the *codebase* — UIDs, references, dead code, refactors — with no running Strapi instance (the one exception: the Pro config-sync tools load the project's Strapi locally when called, the + - Read & analyse (free): `server_info` (running version, licence tier, which tools actually run, how current the index is), `add_project`, `list_projects`, `project_info` (one project in full: versions, plugins verified or not and why, counts, health), `list_content_types`, `list_components`, `list_artifacts`, `get_schema`, `resolve`, `validate_reference`, `find_references`, `list_routes`, `list_unused`, `list_broken_refs`, `coverage`, `find_relation_usages`, `list_refs`, `dependencies`, `depend+ - Config sync through the project's own Strapi (Pro): `config_sync_diff` (the real diff between config/sync and the database, from config-sync itself), `config_sync_export`, `config_sync_import` — they load the project's Strapi the way the plugin's CLI does (they run its code), on a local development database only. The Pro renames and moves also update the config/sync files they concern (permissions, content-manager views), unless `configSync: false` is passed or the user turned it off (strapiDe

version

0.2.1 → 0.2.2

version

0.2.0 → 0.2.1

description

Accurate Strapi project facts (UIDs, schemas, references) for AI agents — no more guessed UIDs. → Strapi codebase intelligence for AI agents (not content CRUD): real UIDs, schemas, refs, refactors.

version

0.1.3 → 0.2.0