Install Praxis

Praxis installs from the Claude interface. You do not need a terminal, npm, administrator rights, a background service or an installer package.

The Claude plugin marketplace is the GitHub repository dfg-inc/praxis-marketplace. For terminal work see also Claude Code CLI setup.

Install from Claude UI (full Praxis)

1. Open Claude and go to Customize → Plugins.
2. Choose Add → Add marketplace.
3. Enter dfg-inc/praxis-marketplace and confirm.
4. Find Praxis in the list and press Add.
5. Check that the components are there (below).
6. Start working: ask Claude to run the getting-started skill of the praxis plugin, or follow First run.

Adding Praxis installs its dependencies automatically: Praxis Runtime (the local MCP server with the praxis_* tools), Praxis BA, Praxis Architect, Praxis Developer and Praxis Quality. Only one Runtime is started.

Status: the Claude Code CLI behaviour on this page is verified (clean install from the public marketplace, dependency resolution, update from alpha.47). The click-by-click flow in the Claude interface is not yet verified by the Praxis team; menu labels can differ slightly between Claude versions. If a label differs, use the in-app search for "Plugins".

Check the components

Ask Claude: "Call praxis_doctor for this folder and show build.version, approval.mode and any errors." You should see version 0.1.0-alpha.49.2. In Claude Code you can also run /plugin and confirm that praxis, praxis-runtime, praxis-ba, praxis-architect, praxis-developer and praxis-quality are enabled.

Which client gets what

Client	Skills from the marketplace	Local Runtime (praxis_* tools)
Claude Code (CLI), Claude Desktop Code, Cowork	Yes	Yes, from the praxis-runtime plugin (a local stdio MCP server)
Claude Desktop Chat	May be available	No from a plugin. Install the separate praxis-runtime.mcpb (below)
Claude Web Chat	Skills only	No. Praxis has no remote service; the Runtime is local

A plugin's local MCP server does not automatically become a tool in ordinary Chat. See Client compatibility.

Protected actions (commits, pushes, merge requests, Jira writes, writing .project, confirming Stories and decisions, recording review decisions) are approved only in the client's own dialog. In Claude Desktop (Chat, Cowork and the Code tab) they are not executed; apply them from the Claude Code CLI in a terminal. See Approvals.

Install one role only

Pick a single role in the plugin list (for example Praxis Quality) and press Add. The role's dependency Praxis Runtime is installed with it; nothing else is.

For developers, the same from a terminal (alternative, not required):

claude plugin marketplace add dfg-inc/praxis-marketplace

claude plugin install praxis@praxis

claude plugin install praxis-quality@praxis

Claude Desktop Chat: connect the Runtime with the MCPB

Use this only if you work in Desktop Chat. It needs the Runtime extension and, for skills, the role ZIPs.

1. Obtain release artifacts

Download each product from its GitHub Releases page. Open the product link below, choose the release you need from that product’s Releases list, then download the named asset. Products publish independently — they do not share one release tag.

Product	Releases	Release asset
Runtime	praxis-runtime Releases	praxis-runtime.mcpb
BA	praxis-ba Releases	praxis-ba.zip
Architect	praxis-architect Releases	praxis-architect.zip
Developer	praxis-developer Releases	praxis-developer.zip
Quality Harness	praxis-quality Releases	praxis-quality.zip

Each release also publishes release-meta.json (version, source SHA, SHA-256, compatibility). Before installing Runtime with one or more role ZIPs, open that file on each chosen release and confirm the declared compatibility requirements for the Runtime and role plugins you plan to use together.

Install only the role ZIPs you need. Products version independently — a BA release does not require a matching Runtime or other Skills tag.

File	What it is
praxis-runtime.mcpb	Praxis Runtime — the shared engine. .mcpb is a Claude Desktop extension bundle (MCP server + user_config).
praxis-ba.zip	BA Skills only
praxis-architect.zip	Architect Skills only
praxis-developer.zip	Developer Skills only
praxis-quality.zip	Quality Harness Skills only; use its supplied access and license terms

Quality Harness is a delivered role package. It is separate from the private Quality Platform, whose planned purpose is multi-project quality history. Harness access does not include Platform access.

Runtime and role plugins are different on purpose. The MCPB talks to Jira and the disk. Role ZIPs tell Claude how to use those tools for one job. Role ZIPs do not embed another Runtime.

2. Install Praxis Runtime

1. Open Claude Desktop.
2. Open Settings.
3. Open Extensions.
4. Open Advanced settings (if shown) and choose Install extension (or Install desktop extension).
5. Select praxis-runtime.mcpb.
6. Enable the extension named Praxis Runtime.

You should see one Praxis Runtime process, not one per role.

3. Configure the Runtime (optional)

1. Still in Settings → Extensions, open Praxis Runtime.
2. Open Settings (extension configuration).
3. Fill in:

UI field	user_config key	Example	Sensitive
Jira Base URL	jira_base_url	https://example.atlassian.net	no
Jira Email	jira_email	[email protected]	no
Jira Project Key	jira_project_key	PRX	no
Jira API Token	jira_token	(paste only in this field)	yes
GitHub Token (Git Delivery)	github_token	(optional PAT, not OAuth)	yes
GitHub API URL	github_api_url	https://api.github.com	no
GitLab Token	gitlab_token	(optional)	yes
GitLab Base URL	gitlab_base_url	https://gitlab.example.com	no

Do not put [email protected]:owner/repo.git in GitHub API URL. That is the Connect Git remote.

4. Save.

How to mint the token: Jira credentials. Never paste the token into chat, Markdown, git, or screenshots.

Claude Desktop stores jira_token in OS secure storage (macOS Keychain, Windows Credential Manager, Linux keychain where supported).

4. Install role plugins (Desktop Chat upload)

1. In Claude, open Customize → Plugins (or Settings → Plugins, depending on the Desktop build).
2. Choose Add / Upload plugins.
3. Select one ZIP, for example praxis-ba.zip.
4. Enable that plugin.
5. Repeat for any other roles you need.

Each ZIP’s .claude-plugin/plugin.json must sit at the archive root. Do not re-zip a parent folder around it.

5. Confirm installation

1. Confirm Praxis Runtime is enabled.
2. Confirm at least one role plugin is enabled.
3. Confirm Skills for that role appear (see Plugins).
4. Open a new Cowork session after enabling anything (see First run).

If a Skill says PRAXIS_RUNTIME_UNAVAILABLE, the Runtime is missing or disabled. Installing another role ZIP will not fix that.

6. Why this order

If you only install…	What happens
Role ZIP, no Runtime	praxis_doctor is absent → PRAXIS_RUNTIME_UNAVAILABLE
Runtime, no role ZIP	Tools exist, but you have no role Skill/prompts
Four Runtimes	Wrong. Uninstall extra MCP copies. One Runtime is enough
All open role ZIPs	Allowed for a solo operator, not required for a team role

7. Developer rebuild (not for end users)

Rebuilders and CI pack from each product repository (npm run pack:mcpb / npm run pack:zip). Ordinary users must download from that product’s public GitHub Releases, not from monorepo Make targets or temporary CI job artifact browsers.

In Claude Desktop, protected actions are not executed. Chat and Cowork show no approval dialog, and the Code tab answers its dialog by itself without showing it. Claude shows the exact preview with APPROVAL_CLIENT_UI_REQUIRED and says it was not applied; nobody is said to have rejected it. Reading, previews, reviews and the rest of the work keep working. Apply protected actions from the Claude Code CLI in a terminal, in the same repository, where the dialog is shown. The extension has no approval settings: Trusted Client and the Approval mode setting were removed in 0.1.0-alpha.49.2. See Approvals.

What you do not need

No Jira (local workflows work without it), no npm install, no administrator rights, no background service, no approval installer, no hardware key. A missing integration is reported as an explicit code (for example JIRA_CONFIG_UNAVAILABLE) and never blocks local work.

Next: Update, Uninstall.