devkit-for-strapi-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y devkit-for-strapi-mcp@0.2.5
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 5 returned a result.
server_info | Returned a result under 0.1 s · 847 characters |
list_projects | Returned a result under 0.1 s · 2 characters |
project_info | Returned a result under 0.1 s · 371 characters |
list_content_types | Returned a result under 0.1 s · 371 characters |
list_components | Returned a result under 0.1 s · 371 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
server_info
The running DevKit server: its version (the one to name in a bug report), the licence tier, which tools really run (without a licence the Pro tools answer an upsell), the indexed roots and how current the index is (`freshness`).
list_projects
List the Strapi projects discovered in the workspace (name, root, Strapi version, counts, `freshness`). Call this first in a multi-project workspace, then pass `from`/`project` to the other tools; project_info gives one project in full.
project_info from, project
One project in full: Strapi version, TS or JS, package manager, API prefix, counts, every local and installed plugin with whether DevKit verifies refs into it (and if not, why), health and freshness. Call it to orient yourself, or when a plugin ref comes back `external`.
add_project path
Index a Strapi project from an ABSOLUTE path: its root or any file/folder inside it (a folder is also scanned downward, for monorepos). Use it when a tool returns `noProject`. Idempotent; returns the projects now known.
refresh cold
Rescan every project from disk and rebuild the index. Rarely needed: each call already re-indexes what changed on disk. For a project added since startup, or edits made outside on a project whose `freshness.diskTracking` is 'off'.
30 more tools
list_content_types from, project
List the real content-type UIDs (e.g. api::article.article) of a Strapi project. Use these exact UIDs — do not invent them.
list_components from, project
List the real component UIDs (e.g. shared.seo) of a Strapi project.
list_artifacts kind, from, project
List the real refs of a project's services, controllers, policies and middlewares (optionally one kind). Use the exact refs returned.
get_model_diagram from, project, components, allPlugins, media, strapiFields, focus, hideCustomFields
The data model as a Mermaid `erDiagram`, read from the schemas: content-types (optionally components) with their fields, one line per association with its cardinalities, media and the plugin types they link to. For a README, a doc or an issue.
get_schema uid, uids, from, project
The real attributes (fields, relations, components) of a content-type or component: use it instead of guessing field names.
resolve ref, from, project
The file(s) defining a Strapi ref, tagged by kind — installed plugins included (in node_modules).
validate_reference ref, kind, from, project
Call this before writing a magic string: is this Strapi ref real in the project, as Strapi registers names (an API file `hasAccess.js` is `has-access`)? valid | unknown (+ didYouMean) | external: in a plugin DevKit cannot verify (project_info says why).
find_references ref, refs, compact, limit, offset, from, project
Every call-site of a ref (or `ref#method`) in the project's own code (src/, config/, database/migrations): the total, then a page of `path:line:col [via] snippet` lines (1-based). A UID written as a plain value counts as `[literal]`; `unresolvedCalls` are the Strapi calls whose UID DevKit cannot read, which may reach it too.
list_routes from, project, plugins, admin, method, path, handler, pipeline
The HTTP route table — the project's routes, createCoreRouter's auto-CRUD and the plugins' (`origin`) — with method, mounted `fullPath`, handler, policies, middlewares, auth and where each is declared. With `pipeline: true`: what a request goes through, in Strapi's order, each step's status (`not-found-by-strapi`: Strapi throws at startup). Use it to explain a 401/403 or a startup error about a policy or middleware.
list_unused file, kinds, from, project
Definitions no Strapi ref reaches: methods, content-types, components, services, policies, middlewares. Only Strapi refs count, so a method called directly in TS still appears — verify before deleting. `onlyArchivedCallers`: only called by migrations Strapi never runs; `requiredByPath`: its file is loaded by path, so the module is used.
coverage
The Strapi call forms DevKit indexes (`via` tag + example) and those it does not (`indexed: false`): whether find_references/list_unused can be trusted for a pattern.
list_broken_refs from, project
Magic strings that point at nothing (refs into plugins DevKit cannot verify are skipped). After apply_edits, it should return none.
config_sync_status key, files, from, project
strapi-plugin-config-sync, from the files only (no database): its version, its options and where each comes from (the warnings say which default exclusions a short `excludedConfig` drops), the sync directory and its files by status — `ok`, `excluded`, `invalid` (not JSON), or of a type not registered here.
config_sync_diff key, type, env, from, project
The diff config-sync's admin page shows, from the real plugin: each entry that differs between config/sync and the database (`different`, `only-in-db`, `only-in-sync-dir`, `invalid-file`: not JSON, empty or not an object), what differs in a few words, and its `likelyDirection` (import | export | unknown) from the file's git history. It includes what a Strapi start changes by itself: after changing a schema, a controller or a route, export those entries and commit them with the code. It loads the project's Strapi the way config-sync's CLI does, which writes to the database as a `strapi develop` start does (schema sync, migrations): a local development database only — a remote one, or a Strapi 4 database under Strapi 5 code, is refused first. A few seconds.
config_sync_export keys, env, from, project
Write entries from the database into config/sync with the plugin's own export, in the exact form config-sync compares. Only entries that differ; one only in config/sync has its file deleted; an `invalid-file` is replaced only when named. Commit the files with the code that caused them. It loads the project's Strapi the way config-sync's CLI does, which writes to the database as a `strapi develop` start does (schema sync, migrations): a local development database only — a remote one, or a Strapi 4 database under Strapi 5 code, is refused first.
config_sync_import keys, reexport, env, from, project
Apply config/sync entries to the database with the plugin's own import (a role, a content-manager view, a setting). `keys` is required, never everything; an entry only in the database is deleted from it; an `invalid-file` is never imported. The entries still different afterwards are exported back (`reexport`), so the diff converges. Refused with NODE_ENV=production. It loads the project's Strapi the way config-sync's CLI does, which writes to the database as a `strapi develop` start does (schema sync, migrations): a local development database only — a remote one, or a Strapi 4 database under Strapi 5 code, is refused first.
find_relation_usages uid, field, from, project
Where a content-type's relation fields are used by name in queries (populate, filters, where), nested levels included. Before retargeting or removing a relation.
list_refs pattern, from, project
Refs matching a glob (`plugin::billing.*`, `api::*`, `*`; only `*` is special), each with the kinds it resolves to.
dependencies ref, transitive, from, project
The refs `ref` uses: relations in its schema, services/controllers it calls…
dependents ref, transitive, from, project
The refs that use `ref`: what would break if it moved or changed.
plan_rename_method ref, method, newName, configSync, from, project
Plan renaming a service/controller method: its declaration, every call-site and, for a controller, the route handlers. Writes nothing: review the plan, then `apply_edits` its `planId`.
plan_rename_entity ref, newName, configSync, from, project
Plan renaming a content-type, component, service, controller, policy or middleware: every call-site and route handler, and the files. The `warnings` list the UIDs Strapi also stores in the database, which the plan does not migrate. Writes nothing: review, then `apply_edits` its `planId`.
plan_move ref, toNamespace, configSync, from, project
Plan moving a service/controller/policy/middleware, or a content-type with its whole resource (service, controller, routes; relation targets repointed), to another namespace: every call-site rewritten, the files relocated. Refused whole if unsafe. Writes nothing: review, then `apply_edits`.
plan_move_entities refs, toNamespace, configSync, from, project
plan_move for several refs to one namespace, in one plan, so the refs between them stay right. Refused whole if any is unsafe.
create_plugin name, from, project
Plan a new local plugin (package.json and a strapi-server.js that registers its folders) and its entry in `config/plugins` (else a warning says what to add). Writes nothing: review, then `apply_edits`.
extract_to_plugin refs, name, configSync, from, project
create_plugin and plan_move in one plan: a new local plugin, and these services/controllers/policies/middlewares moved into it. Refused whole if unsafe.
plan_change_relation uid, field, newTarget, from, project
Plan changing the `target` of a content-type's relation field in schema.json. Refused if the field isn't a relation or the target is unknown; warns about a bidirectional relation's orphaned inverse. Writes nothing: review, then `apply_edits`.
plan_rename_attribute uid, oldName, newName, configSync, from, project
Plan renaming an attribute in schema.json and, for a relation, its populate/filters usages. NOT a complete field rename: object access (`entity.field`, `data: { field }`, destructuring) is not rewritten — the warnings say to review it by hand. Writes nothing: review, then `apply_edits`.apply_edits planId
⚠️ Writes files: applies exactly the reviewed plan (plan_*, create_plugin, extract_to_plugin) by its `planId`. If a file it touches changed since, nothing is written.
apply_rename ref, newName, method, configSync, from, project
⚠️ Writes files: plan_rename_* and apply_edits in one call, without review. Prefer those two to review first.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT AND LicenseRef-PolyForm-Shield-1.0.0 |
|---|---|
| Needs | not stated |
| Source | github.com/PaulRichez/devkit-for-strapi |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-IZwUeJm9Z6/9refCpBSB9MuKq0jroCgJjnjDPvfBAzfOPeR0rmsBnFzC3IkrRvThmn54zx9Acoq3eSFBrXmJpQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/devkit-for-strapi-mcp)
New version out? Ask for a fresh report.