Two surfaces, one engine
The same engine that reads your project powers both — so a fact verified once is true everywhere.
In your editor
- Autocomplete. Inside a magic string, suggests the real UIDs, services, controllers, policies, middlewares, components and route actions for the context at your cursor.
- Diagnostics. Underlines references that don’t exist (with a “did you mean” quick fix) and flags Strapi v4 patterns used in a v5 project.
- Go to definition. Ctrl/Cmd-click a string to jump to the right target — a UID to its schema.json, a route handler to the controller method, a plugin chain to the plugin’s service.
- Find references & CodeLens. A "N references (Strapi)" lens on every definition, including per-method usages the TypeScript server can’t see because strapi.service(...) is typed any.
- Hover. Describes what a string resolves to, with the signature for service methods and usage insights (incoming relations, route handlers, data usages).
- The DevKit panel. Health, routes with what each request goes through in Strapi’s order, the model and the plugins, read from your code, including the plugins installed in node_modules.
- Config Sync. For strapi-plugin-config-sync: your config/sync files with readable names, and the ones the plugin can’t read flagged. With Pro, the real diff with your database, and export or import entry by entry.
Editor features →For your AI agent (MCP)
An MCP server exposes the same ground truth so coding agents query your project’s real values instead of grepping for them. Bundled in the extension and auto-registered — zero config.
Free read & analysis tools
server_infoadd_projectrefreshlist_projectsproject_infolist_content_typeslist_componentslist_artifactsget_schemaresolvevalidate_referencefind_referenceslist_routeslist_unusedlist_broken_refscoveragefind_relation_usageslist_refsdependenciesdependentsconfig_sync_status
MCP setup →