Connect Claude Code
Install the Piyaz plugin in Claude Code over a hosted MCP server with OAuth.
Piyaz is hosted at app.piyaz.ai. The plugin installs into Claude Code once, at the user level, and works in every project you open. No clone required. Run the one-time install, then sign in when prompted (OAuth, once per machine).
Claude Code gets the full Piyaz feature set: the 9 MCP tools, the /piyaz skill, the whole workflow skill set, and the dispatchable agents.
Add the marketplace and install
claude plugin marketplace add FrkAk/piyaz
claude plugin install piyaz@piyazAuthenticate
In Claude Code, run /mcp, select piyaz, and complete the browser sign-in. Claude Code connects to the hosted MCP server over HTTP and runs OAuth on first use. Authentication is once per machine.
Verify
Ask Claude Code:
/piyaz List my projects.Claude returns your project list. An empty list is expected on a fresh account.
Self-host
The plugin ships one MCP server, piyaz, pointing at the hosted app. To use your own server, start it and register a second server alongside it, then sign in:
claude mcp add -s user --transport http piyaz-self-hosted http://localhost:3000/api/mcp
claude mcp login piyaz-self-hostedBoth commands work the same on macOS, Windows, and Linux. -s user registers the server for every project on your machine and stores it in ~/.claude.json; drop the flag to scope it to the current project. Swap http://localhost:3000 for your own origin if you run Piyaz elsewhere, and serve it over HTTPS unless it is on localhost. claude mcp login needs Claude Code v2.1.186 or later; on older versions run /mcp inside a session and authenticate there.
Do not edit the plugin's own .mcp.json; it lives in a version-scoped cache directory that the next plugin update overwrites. For running the server itself, see the self-host guide.
Contributors can install from a local checkout instead of the published marketplace: claude plugin marketplace add ./plugins/claude-code.
What gets installed
| Component | What it does |
|---|---|
| 9 MCP tools | Direct access to the project graph over MCP. See the MCP overview |
/piyaz skill | Auto-invokes when the conversation matches project planning; routes to inline workflows or hands off to a deep-mode workflow |
| Workflow skills | brainstorm, decompose, decompose-feature, decompose-task, manage, onboarding, and composer for end-to-end task orchestration |
| Dispatchable agents | Most workflows also run as agents via the Task tool (brainstorm, decompose, decompose-feature, decompose-task, manage, onboarding, the composer phase agents, and review), so the main skill can hand off work in a clean per-agent context |
Claude Code is the only platform that ships composer (end-to-end task orchestration), because composer depends on a subagent dispatch primitive the other platforms do not yet have. See Agentic workflows for how the skills and agents work together.
Pro plan: composer runs inside a Claude Code Dynamic workflow, which is off by default on Pro. Before you run /piyaz:composer, turn it on from the Dynamic workflows row in /config (requires Claude Code v2.1.154 or later). On Max, Team, Enterprise, and Anthropic API or cloud-provider access it is already on.
Keep the plugin updated
Turn on auto-update so Claude Code pulls new Piyaz releases for you.
Open the plugin manager
Run /plugin in Claude Code, then move to the Marketplaces tab.
Enable auto-update on the piyaz marketplace
Select the piyaz marketplace from the list and choose Enable auto-update.
Auto-update is set per marketplace, not per plugin. The piyaz marketplace ships only the Piyaz plugin, so enabling it there keeps Piyaz current. Claude Code checks for updates at startup; when a new version lands it prompts you to run /reload-plugins to apply it.
For third-party marketplaces like piyaz, auto-update is off by default, so you stay on the installed version until you turn it on.
Next Steps
- MCP Overview -- tool workflows and server architecture.
- Quickstart -- create your first project.
Last updated