Marketplace, releases and product catalog
Praxis is distributed in two ways that you can combine by client.
The Claude plugin marketplace
The Claude plugin marketplace is the GitHub repository dfg-inc/praxis-marketplace (marketplace name praxis). In Claude: Customize → Plugins → Add → Add marketplace → dfg-inc/praxis-marketplace → Praxis → Add. See installation.
| Plugin | Role |
|---|---|
praxis | The complete set. Installs the five plugins below as dependencies |
praxis-runtime | The local MCP server (praxis_* tools). Installed automatically with any role |
praxis-ba, praxis-architect, praxis-developer, praxis-quality | Role skills, installable separately |
A role plugin declares its dependency on praxis-runtime, so installing one role never leaves it without tools and only one Runtime runs. The marketplace repository contains only the plugins; this website is the single source of documentation. How it is built and released: Marketplace distribution.
A plugin's local MCP server is not an ordinary-Chat tool. For Claude Desktop Chat install the Runtime from the release praxis-runtime.mcpb; Claude Web Chat gets skills only. Praxis has no remote service. See Client compatibility.
GitHub Releases
| Product | Distribution | Access |
|---|---|---|
| Runtime | Runtime Releases, praxis-runtime.mcpb | Shared engine |
| Business Analyst | BA Releases, praxis-ba.zip | Apache-2.0 harness |
| Architect | Architect Releases, praxis-architect.zip | Apache-2.0 harness |
| Developer | Developer Releases, praxis-developer.zip | Apache-2.0 harness |
| Quality Harness | Quality Releases, praxis-quality.zip | Delivered role package |
| Quality Platform | Request private access | Separate planned private multi-project history product |
Products publish independently on GitHub Releases. Check each chosen Release's release-meta.json for version, source SHA, SHA-256, and compatibility before installing or updating; shared tags across products are not required. Do not install from temporary CI job artifacts or old monorepo archives. The Core libraries are dependencies, not another end-user installation.
Continue with installation, updates, or the catalog.