Pluxx — Development skill for Claude Code

pluxx

**Turn a raw MCP into a native plugin across Claude Code, Cursor, Codex, and OpenCode.**

Import a raw MCP or an existing host-native plugin, keep one maintained source project, and compile native outputs for **Claude Code, Cursor, Codex, and OpenCode** instead of maintaining four separate plugin codebases.

Pluxx is the authoring, maintenance, and compilation layer for teams that want one source of truth instead of four drifting per-host plugin repos. Start with `init`, or use `pluxx autopilot` when you want the one-shot path.

Raw MCP access is usually not enough. Most products still need workflow grouping, stronger instructions, hooks, commands, auth/setup guidance, and honest host-native packaging. Pluxx is the layer that makes that repeatable.

• Start here: docs/start-here.md
• Docs: docs.pluxx.dev
• Website: pluxx.dev

Current Proof

Proof claims are tiered and freshness-checked. See [Proof freshness and evidence tiers](./docs/proof-freshness.md) and the machine-readable [proof manifest](./docs/proof-manifest.json); April/May host runs remain available as explicitly historical evidence.

If you want the fastest way to see what is already real, start with these:

• Release distribution proof map
  • the current source of truth for what Pluxx ships today, the local build/install/sync/prove lane for the primary fronts, and what still belongs to marketplace or trust-layer work
• Proof and install guide
  • the shortest public path to the current demos plus one-command install paths for the released self-hosted plugin
• Self-hosted core-four proof
  • example/pluxx rebuilt, installed, and verify-install checked across Claude Code, Cursor, Codex, and OpenCode
• Docs Ops core-four proof
  • the flagship example/docs-ops