Installing Deliberation as a Kiro Power
Kiro (external) (AWS) packages reusable tool + steering bundles as
Powers. The Deliberation Power ships a plugin.json (the Agent Plugins manifest
Kiro uses for new Powers), an mcp.json, and the legacy POWER.md and steering/
files at the repo root, all generated by scripts/sync-hosts.js from the canonical
sources (docs/tool-guide.md, rules/triggers.md). A Power activates
on-demand when its keywords match your task, so the MCP tools load only when a
delegation is actually relevant.
Install
The install steps for Kiro are on the install page, with every other host. This page has the rest: what the plugin ships, provider keys, updating and notes.
Provider credentials
The MCP server (npx -y @antonbabenko/deliberation-mcp, stdio) reads provider
credentials from the host environment. Set whichever providers you use:
| Provider | How it authenticates |
|---|---|
| GPT (Codex) | Codex CLI auth (codex login, e.g. ChatGPT - codex login --device-auth on a remote machine; or CODEX_ACCESS_TOKEN; else CODEX_API_KEY) |
| Gemini | GEMINI_API_KEY (Google AI Studio key). Opt-in fallback: the Antigravity CLI (agy) - see the terms note below |
| Grok (xAI) | XAI_API_KEY |
| OpenRouter | OPENROUTER_API_KEY (advisory-only; declare models in ~/.config/deliberation/config.json) |
Gemini note: with no key, Gemini falls back to the Antigravity CLI (agy). Read the
Antigravity terms (external) first. Section 6 lists "Using third
party software, tools, or services to access the Service (e.g. using OpenClaw with
Antigravity OAuth)" as a breach that "may be grounds for suspension or termination of your
Antigravity and/or Gemini CLI accounts". Deliberation drives agy as third-party software.
mcp.json declares an empty env: {}; the bridges pick the keys up from the
process environment Kiro launches the server in. You only need the providers you
intend to call - missing keys just disable that one provider.
Activation keywords
The Power loads when your task mentions any of its keywords:
architecture review, security review, second opinion, consensus, council,
code review, plan review, debug, writing editor, edit this post, in my voice,
sound like me, grok, openrouter, gpt, gemini, deliberationOnce loaded, the steering files tell Kiro when to call each tool (ask-all,
consensus, ask-gpt / ask-gemini / ask-grok / ask-openrouter) and each
expert persona (architect, plan-reviewer, scope-analyst, code-reviewer,
security-analyst, researcher, debugger, writing-editor).
Submitting to the Kiro registry
Submit at kiro.dev/registry/submit (external) with resource
type Power: name, email, a 3-4 word use case, the public repository URL, an
optional logo (assets/logo-mark.svg) and an optional
description. The Kiro team reviews submissions and contacts candidates. The form's
checklist (checked 2026-11-18): the Power is complete, tested and unique; any MCP
server it uses is generally available; plugin.json has $schema, name, version,
description, author, keywords and an SPDX license; and the README links a
Privacy Policy and a support contact. The generated plugin.json carries those fields
(its version follows version.json), the README links PRIVACY.md
and the issue tracker, and POWER.md keeps its ## License and support footer for
the legacy format. Submitting the form is a separate, manual step.
Updating
Kiro starts the server with npx -y @antonbabenko/deliberation-mcp. The npm package does not
include this repository's scripts/ folder. After an update:
# stop the dashboard; prints "no running dashboard" if none runs
npx -y @antonbabenko/deliberation-mcp dashboard --stop
# drop the cached old build of this package (macOS, Linux)
find ~/.npm/_npx -type d -path '*/@antonbabenko/deliberation-mcp' -prune -exec rm -rf {} +On Windows, dashboard --stop is not supported: close the dashboard process first, then
delete the @antonbabenko\deliberation-mcp folders under %LocalAppData%\npm-cache\_npx.
Then restart the Deliberation MCP server in Kiro, or restart Kiro, so the next Power
activation runs the new version. In a clone of this repository,
bash scripts/commands/reload-mcp.sh clears the cached package, restarts the dashboard
and audits the running Deliberation processes.
If you use the dashboard, start it again on the new version with
npx -y @antonbabenko/deliberation-mcp dashboard.
Notes / unverified
- The official docs (kiro.dev/docs/powers, /create, /registry/submit, /docs/steering)
confirm:
POWER.mdfrontmatter fields (name,displayName,description,keywords,author), the root-levelmcp.jsonshape (the Agent Plugins schema requires$schemaandtype: "stdio"), the rootplugin.jsonmanifest, thesteering/subdirectory,inclusion: alwayssteering frontmatter, the Add power from GitHub install flow, and the License / Privacy / Support footer requirement. - [unverified] Whether Kiro reads per-server
envsubstitution like${VAR}inside a Power'smcp.json(Kiro's example shows${SUPABASE_URL}, but Deliberation reads keys straight from the process env, so we shipenv: {}). Confirm at kiro.dev/docs/powers/create (external) if you want to pin keys inmcp.jsoninstead of the environment.