The short answer
Most readers should only read one of those three.
Use Docs Ops when
- you want the clearest public proof page
- your plugin rewrites, reviews, or improves docs/content
- you care about install and
verify-installproof across Claude Code, Cursor, Codex, and OpenCode - you want to see read-only access separated from a private publish lane
Use Exa when
- your product already has an MCP
- you want richer workflow packaging around research or search
- you care about specialist agents and explicit commands
- you want a public example that is not a docs workflow
Use Platform Change Ops when
- your plugin has more enterprise/runtime complexity
- you need local stdio runtime packaging
- you need readiness gates, hooks, permissions, and specialist agents together
- you want to pressure-test Pluxx itself, not just copy a minimal product example
Long-tail examples
These are still useful, but they should not be the first pages most people read:- Self-hosting Pluxx Plugin: use when you want to see Pluxx package itself.
- Sumble Example: use when you want a live commercial MCP example with bearer auth.
- Firecrawl, Sumble, and PlayKit-style Examples: use when you need import patterns for large tool surfaces or custom header auth.