@experia-labs/plugin-dev-mcp

A Model Context Protocol server that helps developers build plugins for the Experia platform. Plug it into Claude Code (or any MCP-aware IDE) and ask things like:

"Generate a starter manifest for an organizer-tool plugin called acme.standup."

"Validate this manifest" (paste it)

"Which scope do I need to call POST /messaging/send?"

"Why is my webhook returning 401?" (paste payload + header + secret)

The same validation rules used by the platform's publish endpoint run inside this server — if validate_manifest passes locally, your POST /developer-portal/plugins/:id/versions call will too.

Install + run via Claude Code

claude mcp add experia-plugin-dev -- npx -y @experia-labs/plugin-dev-mcp

Or, while developing locally:

cd creatoros-api/packages/plugin-dev-mcp
npm install
npm run build
claude mcp add experia-plugin-dev -- node $(pwd)/dist/cli.js

To use it inside a non-Claude MCP client, point the client at the same binary and use stdio transport.

Tools

| Tool | What it does | |------|--------------| | list_scopes | Every OAuth-style scope, what it grants, which endpoints it unlocks. | | list_events | Lifecycle + domain webhook events with example payloads. | | list_extension_slots | Where in the host UI your iframe can render. | | list_api_endpoints | Every /plugin-api/v1 endpoint and the scope it requires. | | validate_manifest | Runs the platform's publish-time validator on your manifest. | | get_starter_manifest | Scaffolds a manifest (minimal / attendee-app / organizer-tool). | | verify_webhook_signature | Verifies an X-Experia-Signature header against a payload + secret. Use to debug 401/403s. |

Resources

| URI | Contents | |-----|----------| | experia://docs/overview | Plugin lifecycle, manifests, webhooks, /plugin-api/v1. | | experia://docs/manifest | Field-by-field manifest reference. | | experia://docs/webhooks | Signature scheme, replay window, retries. |

Library use

The same helpers are exported from the package root if you want to use them in CI checks or your own tooling:

import {
  validateManifest,
  generateStarterManifest,
  verifyWebhookSignature,
} from '@experia-labs/plugin-dev-mcp';

Develop

npm install
npm run build       # compile TS
npm test            # 25+ unit tests
npm run verify      # tsc --noEmit

Static data files in src/data/ (scopes, events, slots, API endpoints) must stay in sync with their counterparts in creatoros-api/src/features/plugin-platform/. The data/registry.spec.ts tests catch obvious drift; the manifest/validate.spec.ts tests cover the validator.