Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.PaulRichez/devkit-for-strapi-mcp

NPM · DEVKIT-FOR-STRAPI-MCP

Strapi codebase intelligence for AI agents (not content CRUD): real UIDs, schemas, refs, refactors.

0 this week 74 Trust /100

Last scanned (23 hours ago)

Scores higher than 49% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6090 tokens (~174/item across 35 items; 35 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability check failed: the tool surface changed between 0.2.2 and 0.2.5: 2 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 35 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93.

  • 20 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 90.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93.

  • 11 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.4 → 0.2.5 functional
  • 9 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 8 Nov 26 −2

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 77.

  • 7 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/devkit-for-strapi-mcp@0.2.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 35 exposed · ~5,586 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_project ~86

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.

NameTypeReqDescription
pathstringyesAbsolute path to the Strapi project root, or to any file/folder inside it.

No output schema declared.

No examples provided.

apply_edits ~65

⚠️ 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.

NameTypeReqDescription
planIdstringyesThe planId from a plan_* result.

No output schema declared.

No examples provided.

apply_rename ~253

⚠️ Writes files: plan_rename_* and apply_edits in one call, without review. Prefer those two to review first.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
methodstring–The method to rename; omit to rename the entity.
newNamestringyesThe new method name, or the UID's new last segment.
projectstring–A project name or root, when no path is at hand.
refstringyesA Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…

No output schema declared.

No examples provided.

config_sync_diff ~302

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.

NameTypeReqDescription
envstring–NODE_ENV for the run (default development).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
keystring–One entry, `<type>.<name>`: every difference, and both sides when they fit.
projectstring–A project name or root, when no path is at hand.
typestring–Only one type (`admin-role`, `user-role`, `core-store`…).

No output schema declared.

No examples provided.

config_sync_export ~215

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.

NameTypeReqDescription
envstring–NODE_ENV for the run (default development).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
keysarray–The entries to export (default: every difference).
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

config_sync_import ~256

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.

NameTypeReqDescription
envstring–NODE_ENV for the run (default development).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
keysarrayyesThe entries to import, `<type>.<name>`.
projectstring–A project name or root, when no path is at hand.
reexportboolean–Export back the entries still different afterwards (default true).

No output schema declared.

No examples provided.

config_sync_status ~173

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.

NameTypeReqDescription
filesboolean–List every file with a readable name and status (default: counts).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
keystring–One file's content, by `<type>.<name>` (user-role.public).
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

coverage ~46

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_plugin ~120

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`.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
namestringyesPlugin name, kebab-case.
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

dependencies ~158

The refs `ref` uses: relations in its schema, services/controllers it calls…

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
refstringyesA Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…
transitiveboolean–Follow the chain (default false).

No output schema declared.

No examples provided.

dependents ~158

The refs that use `ref`: what would break if it moved or changed.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
refstringyesA Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…
transitiveboolean–Follow the chain (default false).

No output schema declared.

No examples provided.

extract_to_plugin ~180

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.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
namestringyesNew plugin name, kebab-case.
projectstring–A project name or root, when no path is at hand.
refsarrayyesThe refs to move into it.

No output schema declared.

No examples provided.

find_references ~273

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.

NameTypeReqDescription
compactboolean–One line per hit (default true); false for full objects.
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
limitinteger–Max references per ref (default 50).
offsetinteger–Skip this many (pagination).
projectstring–A project name or root, when no path is at hand.
refstring–A Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…
refsarray–Several refs at once.

No output schema declared.

No examples provided.

find_relation_usages ~130

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.

NameTypeReqDescription
fieldstring–A relation field name; omit for all relations.
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
uidstringyesA content-type UID, e.g. api::article.article

No output schema declared.

No examples provided.

get_model_diagram ~249

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.

NameTypeReqDescription
allPluginsboolean–Every installed plugin type, not only those linked to (default false).
componentsboolean–Include components (default false).
focusarray–Only these UIDs and the types they link to.
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
hideCustomFields––Leave out custom fields: true for all, or their names (listed under `customFields` in the answer). Default: none.
mediaboolean–Media fields → the upload plugin's File (default true).
projectstring–A project name or root, when no path is at hand.
strapiFieldsboolean–The fields Strapi adds: createdAt, updatedAt, publishedAt, createdBy/updatedBy (default false).

No output schema declared.

No examples provided.

get_schema ~114

The real attributes (fields, relations, components) of a content-type or component: use it instead of guessing field names.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
uidstring–A content-type or component UID.
uidsarray–Several UIDs to fetch in one call.

No output schema declared.

No examples provided.

list_artifacts ~103

List the real refs of a project's services, controllers, policies and middlewares (optionally one kind). Use the exact refs returned.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
kindstring–Only this kind (default: all four).
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_broken_refs ~89

Magic strings that point at nothing (refs into plugins DevKit cannot verify are skipped). After apply_edits, it should return none.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_components ~80

List the real component UIDs (e.g. shared.seo) of a Strapi project.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_content_types ~94

List the real content-type UIDs (e.g. api::article.article) of a Strapi project. Use these exact UIDs — do not invent them.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_projects ~63

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_refs ~112

Refs matching a glob (`plugin::billing.*`, `api::*`, `*`; only `*` is special), each with the kinds it resolves to.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
patternstringyesGlob, e.g. plugin::billing.* or api::*
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_routes ~272

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.

NameTypeReqDescription
adminboolean–Include admin-panel routes (default false).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
handlerstring–Only handlers containing this (`api::article.article.find`).
methodstring–Only this HTTP method.
pathstring–Only routes matching this pattern, a part of it, or a concrete URL (`/api/articles/12`).
pipelineboolean–Add each route's pipeline (needs method, path or handler; at most 20 routes).
pluginsboolean–Include the plugins' routes (default true).
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

list_unused ~174

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.

NameTypeReqDescription
filestring–Only this file, absolute or relative to the project root (default: the whole app).
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
kindsarray–Restrict to certain kinds (default: all).
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

plan_change_relation ~149

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`.

NameTypeReqDescription
fieldstringyesThe relation field.
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
newTargetstringyesThe new target content-type UID.
projectstring–A project name or root, when no path is at hand.
uidstringyesThe content-type UID.

No output schema declared.

No examples provided.

plan_move ~215

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`.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
refstringyesAn artifact ref (plugin::src.helper) or a content-type UID.
toNamespacestringyesplugin::dst or api::foo.

No output schema declared.

No examples provided.

plan_move_entities ~176

plan_move for several refs to one namespace, in one plan, so the refs between them stay right. Refused whole if any is unsafe.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
refsarrayyesThe refs to move together.
toNamespacestringyesplugin::dst or api::foo.

No output schema declared.

No examples provided.

plan_rename_attribute ~220

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`.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
newNamestringyesNew attribute name.
oldNamestringyesCurrent attribute name.
projectstring–A project name or root, when no path is at hand.
uidstringyesThe content-type UID.

No output schema declared.

No examples provided.

plan_rename_entity ~231

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`.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
newNamestringyesThe new last segment: item makes api::product.product api::product.item.
projectstring–A project name or root, when no path is at hand.
refstringyesThe UID or ref (api::product.product, shared.seo).

No output schema declared.

No examples provided.

plan_rename_method ~203

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`.

NameTypeReqDescription
configSyncboolean–With config-sync: also update the config/sync files this refactor concerns (roles' permissions, content-manager views). Default: the user's setting, true unless turned off. false when config/sync isn…
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
methodstringyesThe current method name.
newNamestringyesThe new method name.
projectstring–A project name or root, when no path is at hand.
refstringyesThe service/controller ref (api::page.notifier).

No output schema declared.

No examples provided.

project_info ~121

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`.

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.

No output schema declared.

No examples provided.

refresh ~81

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'.

NameTypeReqDescription
coldboolean–Also read every installed plugin again, ignoring the cache (slower; default false).

No output schema declared.

No examples provided.

resolve ~149

The file(s) defining a Strapi ref, tagged by kind — installed plugins included (in node_modules).

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
projectstring–A project name or root, when no path is at hand.
refstringyesA Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…

No output schema declared.

No examples provided.

server_info ~60

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`).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_reference ~216

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).

NameTypeReqDescription
fromstring–A path inside the project (the file you are editing; relative to its root with `project`), in a multi-project workspace.
kindstring–Check it as this kind only (`method`: the service/controller a handler or method call goes through).
projectstring–A project name or root, when no path is at hand.
refstringyesA Strapi ref: a content-type or component UID (api::article.article, shared.seo), a service/controller/policy/middleware ref (plugin::users-permissions.user, global::is-owner) or a route handler (api…

No output schema declared.

No examples provided.

Install

How do I install the io.github.PaulRichez/devkit-for-strapi-mcp server?

io.github.PaulRichez/devkit-for-strapi-mcp runs locally as an npm package, launched with npx -y devkit-for-strapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · devkit-for-strapi-mcp

# add to Claude Code
claude mcp add paulrichez-devkit-for-strapi-mcp -- npx -y devkit-for-strapi-mcp
Common questions

What is the io.github.PaulRichez/devkit-for-strapi-mcp server?

io.github.PaulRichez/devkit-for-strapi-mcp is listed in the public MCP registry as io.github.PaulRichez/devkit-for-strapi-mcp. Strapi codebase intelligence for AI agents (not content CRUD): real UIDs, schemas, refs, refactors. This page covers its npm package (devkit-for-strapi-mcp).

Is the io.github.PaulRichez/devkit-for-strapi-mcp server safe to use?

io.github.PaulRichez/devkit-for-strapi-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.PaulRichez/devkit-for-strapi-mcp server expose?

io.github.PaulRichez/devkit-for-strapi-mcp exposes 35 tools: server_info, list_projects, project_info, add_project, refresh, and 30 more. Their descriptions and schemas cost roughly 5,586 tokens of context every time the server is loaded.

Is the io.github.PaulRichez/devkit-for-strapi-mcp server still maintained?

io.github.PaulRichez/devkit-for-strapi-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.PaulRichez/devkit-for-strapi-mcp server under?

io.github.PaulRichez/devkit-for-strapi-mcp declares the MIT AND LicenseRef-PolyForm-Shield-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the io.github.PaulRichez/devkit-for-strapi-mcp server?

VerifyMCP ran 16 checks on io.github.PaulRichez/devkit-for-strapi-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.