CLI Plugins
Konductro's CLI plugins bring the platform into the developer's IDE. They connect Claude Code and Amazon Q to Konductro via MCP (Model Context Protocol), giving the AI in the editor access to project context, task details, and delivery workflows.
Why CLI Plugins Exist
Some workflows require access to the actual codebase — not an abstraction of it:
- Technical analysis needs to read real files, understand existing patterns, and trace dependencies
- Story decomposition needs to explore the codebase to scope tasks to specific files and repos
- Development benefits from having task context, acceptance criteria, and architectural notes available in the editor
These operations run on the developer's machine, where the code lives. The CLI plugin bridges the gap between the local codebase and Konductro's planning data.
Supported IDEs
| IDE | Plugin | Transport |
|---|---|---|
| Claude Code | @conductor/claude-plugin | MCP server (stdio) |
| Amazon Q | @conductor/q-plugin | MCP server (stdio) |
Both plugins offer the same capabilities. The choice depends on which IDE the developer uses.
What the Plugins Provide
Skills (slash commands)
| Skill | Purpose |
|---|---|
/technical-analysis | Run a technical analysis against the local codebase |
/decompose | Break a story into technical tasks by exploring real code |
/start-work | Start work on an assigned task (branch + spec push) |
/prototype | Build a UX prototype from design system context |
/profile-repository | Scan and register the codebase profile with Konductro |
MCP Tools
The plugins also expose individual MCP tools that the AI in the editor can call during conversation — listing tickets, loading context, submitting results, and more.
How It Works
The plugin runs as an MCP server using stdio transport. When the developer starts a conversation in their IDE, the AI can call Konductro tools to:
- Pull context — load task details, acceptance criteria, architectural notes, approved artefacts
- Execute workflows — start work, submit decomposition results, create PRs
- Push data back — submit technical analysis documents, repository profiles, prototype builds
All communication goes through the Konductro REST API using a personal CLI token. No direct database access, no secrets exposed to the IDE.
See Installation to get started or the Tools Reference for the full list of available tools.