strapi-plugin-development

Coding rules for developing a Strapi v5 plugin with separate administration and server parts. Strapi is a framework for managing content and exposing it through APIs.

In plain words
What is it for?
For adding plugin features, admin-panel pages, API endpoints, validation, translations, and business logic in the correct project locations.
Why use it?
They provide consistent patterns for plugin registration, admin navigation, internationalisation, controllers, routes, and service-layer code.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/virtuslab-open-source/strapi-plugin-mcp/strapi-plugin-development
Clone the repo
git clone --depth 1 https://github.com/VirtusLab-Open-Source/strapi-plugin-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 591 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00591
Opus 5 $0.00000 $0.00296
Sonnet 5 $0.00000 $0.00118
Haiku 4.5 $0.00000 $0.00059

Measured 2d ago against content hash 22aa4a30f1d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

strapi-plugin-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/strapi-plugin-development.mdc · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Strapi Plugin Development Guidelines

Plugin Registration

Strapi v5 Plugin Architecture

  • Dual export system: admin and server components are separate
  • Admin components use React and Strapi Design System
  • Server components follow Strapi's controller/service/route pattern

Admin Panel Integration

  • Use @strapi/design-system components for consistent UI
  • Follow Strapi's admin panel patterns for navigation and layout
  • Implement proper internationalization using admin/src/translations/

API Development

Service Layer

Plugin Configuration

  • Plugin metadata is defined in package.json under the "strapi" key
  • Plugin kind is set to "plugin"
  • Display name and description should be meaningful

Build and Distribution

  • Use @strapi/sdk-plugin for building
  • Built files go to dist/ directory
  • Both CommonJS and ESM formats are supported
  • TypeScript declarations are generated automatically

Testing

  • Type checking: pnpm test:ts:front and pnpm test:ts:back
  • Plugin verification: pnpm verify
  • Manual testing in development: pnpm watch

MCP Integration Specifics

  • This plugin integrates Model Context Protocol functionality
  • Uses @modelcontextprotocol/sdk for MCP operations
  • Provides content type introspection and system information
  • Handles MCP events through dedicated controllers

Read the full file on GitHub · 68 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 68 lines · 0 tokens per session scan A 22aa4a30f1d7

Subscribe to this mod's changes

strapi-plugin-development is a cursor rule published in the GitHub repository VirtusLab-Open-Source/strapi-plugin-mcp (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 591 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.