lukewo

GitHub and git integration driven by the GitHub CLI (gh) and git. Runs a local MCP server for the full pull request review lifecycle from both sides - as a reviewer (read diffs, reviews and threads, list review requests, approve/request-changes/comment, inline comments, replies, resolve threads) and as an author (create/edit PRs, request reviewers, mark ready, check CI, merge) - plus read tools for issues and PRs, and local git operations (status, log, diff, branch, add, commit, push, pull, fetch, merge, stash, checkout) against the open workspace repo. Uses your existing gh authentication (no tokens stored by the power). Reads and writes, with two safety boundaries: a command allow-list and a deny check that refuses history rewrites (force push), destructive local loss (reset --hard, clean, branch -D), gh auth/config changes, and merges without explicit confirmation.

Read-only Jira Cloud integration over the Jira REST API v3. Exposes a local MCP server with get_issue, search_issues (JQL), and get_issue_comments so Jira ticket context can be pulled into Kiro while coding. Uses a per-user Jira API token (no Rovo credits). Strictly read-only: it never creates, updates, transitions, comments on, or otherwise modifies Jira tickets.

Read-only Sentry integration over the Sentry REST API. Exposes a local MCP server with list_projects, search_issues, search_logs, get_issue, get_event, and get_issue_tags so crash reports, stack traces, tag breakdowns and structured logs (Explore > Logs, paged and saved as Serilog-style .log files) can be pulled into Kiro while coding. Uses a per-user Sentry auth token. Strictly read-only: it performs HTTP GET requests only and never resolves, ignores, assigns, comments on, or otherwise modifies anything in Sentry.