For your AI agent (MCP)
The same engine, exposed over the Model Context Protocol so coding agents (Claude Code, Copilot agent mode, Cursor, …) query your project’s real values instead of inventing them.
- VS Code, Cursor, Windsurf, Antigravity — the server is bundled in the extension and auto-registered with the editor’s MCP support. Nothing to configure: install the extension and your agent can use the tools.
- Other MCP clients — run
devkit-for-strapi-mcpas a stdio server, passing your project path. It also accepts the workspace folder via the client’srootscapability, and a tool (add_project) to register a project on demand.
Know — read the project’s truth: list_projects, list_content_types,
list_components, list_artifacts, get_schema, resolve,
validate_reference, find_references, list_routes.
Understand — health & impact: list_unused (dead code), list_broken_refs,
coverage, find_relation_usages, list_refs, dependencies / dependents
(the dependency graph, for cut analysis).
Refactor (Pro) — plan → review → apply: plan_rename_method /
plan_rename_entity, plan_move / plan_move_entities, plan_change_relation,
plan_rename_attribute, create_plugin, extract_to_plugin, then apply_edits
/ apply_rename.
Every refactor returns a contractual, reviewable plan (text edits + file creates/renames/deletes + content fingerprints). Applying is explicit and safe by construction: the executor is confined to your discovered project root(s) (symlink-resolved), refuses to silently overwrite, verifies the fingerprints first (a stale plan is rejected), is best-effort transactional, and self-verifies afterward. Garantir, ne pas deviner — applied to writes too.