WhyKit
What it does
Read-only decisions and evidence from a Git vault, and which decisions a code change touches.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
archify
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhyKit for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "whykit": { "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the WhyKit tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "whykit": { "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } }Quit Claude and open it again
Try it
Use WhyKit and tell me what you can do for me, then show me one thing✓ If Claude says it is using WhyKit or shows a WhyKit tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect WhyKit yet
WhyKit runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect WhyKit
- Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
- Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhyKit for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user whykit -- uvx whykit --root --max-sensitivity internal 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the WhyKit tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user whykit -- uvx whykit --root --max-sensitivity internalType /mcp in Claude Code
You should see WhyKit listed as connected
Try it
Use WhyKit and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using WhyKit or shows a WhyKit tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhyKit for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "whykit": { "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the WhyKit tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Cursor’s MCP settings file
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{ "mcpServers": { "whykit": { "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } }Open the AI chat in Cursor in Agent mode
Try it
Use WhyKit and tell me what you can do for me, then show me one thing✓ If Cursor says it is using WhyKit or shows a WhyKit tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server WhyKit for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "whykit": { "type": "stdio", "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the WhyKit tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open VS Code’s MCP settings file
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{ "servers": { "whykit": { "type": "stdio", "command": "uvx", "args": [ "whykit", "--root", "--max-sensitivity", "internal" ] } } }Open the AI chat in VS Code in Agent mode
Try it
Use WhyKit and tell me what you can do for me, then show me one thing✓ If VS Code says it is using WhyKit or shows a WhyKit tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user whykit -- uvx whykit --root --max-sensitivity internalClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"whykit": {
"command": "uvx",
"args": [
"whykit",
"--root",
"--max-sensitivity",
"internal"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"whykit": {
"command": "uvx",
"args": [
"whykit",
"--root",
"--max-sensitivity",
"internal"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"whykit": {
"type": "stdio",
"command": "uvx",
"args": [
"whykit",
"--root",
"--max-sensitivity",
"internal"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- 42/wk
- Connection
- Runs on your computer
- Latest versioni
- 0.5.1
- Categoryi
- Developer tools
- Published to registryi
- Nov 14, 2026
- Code last changedi
- Nov 15, 2026
- Maker
- CometWeb-io
- Packages
pypi: whykit- Website
- whykit.cometweb.io
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CometWeb-io, which owns the repo
- ✓ Pass
Still maintained
Code last changed yesterday
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for whykit@0.5.1
Checks only this package version, not every dependency · checked Nov 15, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/cometweb-io-whykit)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 77% of the other 5955 servers in this category
- Published to the registry more recently than 96% of the other 5955 servers in this category
- Basic checks equal to or better than 100% of the other 5955 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is WhyKit safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed yesterday, and the latest version (0.5.1) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one WhyKit | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
WhyKit
Know why every decision was made.
Decisions about code, product or go-to-market get made for reasons that end up in someone's head or an old thread. WhyKit keeps those decisions and the sources behind them as Markdown in Git. It flags a decision when a source changes or a review is due, shows which decisions a pull request touches, and lets Claude Code, Codex or Cursor look them up before they act, so an agent doesn't "fix" something that was deliberate.
Open source from CometWeb · Apache-2.0 · No runtime dependencies · Your data stays Markdown
Live demo · Tutorial · Connect agents · Docs · Roadmap
What it does
Each decision cites its sources (E-001) and declares the code it governs (applies_to: ["src/payments/**"]). Before a change lands, one command answers *which decisions does this touch, and has anything they rest on changed?*
$ whykit affected --root examples/payments --today 2026-11-12 \
--files src/payments/ledger.py src/webhooks/refunds.py README.md WhyKit affected — 3 changed files · 2 decisions apply · 1 needs review · 1 file not covered by any decision D-001 review Store money as integer cents files: src/payments/ledger.py
- a cited source was retired D-003 applies Make every webhook handler idempotent files: src/webhooks/refunds.py not covered by any decision: README.md 1 live decision(s) declare no applies_to scope: D-005
That is real output from the synthetic payments example; a test keeps this block in step with the code. The ledger decision rests on an audit checklist that has since been replaced, so its reasoning needs a look before this change merges. WhyKit says what it checked and what it did not: uncovered files and unscoped decisions are listed, and it never claims a change is safe.
- Sources get stable IDs and can be retired or replaced; captured sources are pinned by their bytes.
- Decisions cite sources, declare their scope, carry an owner and a review date, and are append-only: you supersede, you don't rewrite.
- Changes are mapped to decisions by
whykit affected, locally, in CI and by agents, with review signals for retired, missing, stale or changed sources (including source files the change itself modifies) and overdue or failed reviews. Scopes can be suggested from Git history. - Agents read the same files through a read-only MCP server, and
whykit connecttells them to ask before they edit.
Try it
Install uv (0.13.4+) and use Python 3.11+. This creates a *vault*, a folder of Markdown files, with one source and one draft decision that cites it:
uv tool install whykit
Create a vault.
whykit init my-ledger
Record a source, then a draft decision that cites it.
whykit new --root my-ledger evidence \ --source "Support ticket export, Q3" --type dataset \ --location "https://example.com/exports/q3-tickets.csv" \ --claims "Most onboarding tickets mention SSO" whykit new --root my-ledger decision "Ship SSO before audit logs" \ --owner Platform --status draft --source E-001
See the connection, then check the vault.
whykit trace --root my-ledger --decision D-001 whykit lint --root my-ledger whykit review --root my-ledger list --due-days 120
<!-- quickstart:end -->
The trace shows the decision and the source it cites:
D-001 06-decisions/d-001-ship-sso-before-audit-logs.md (draft)
E-001 active
The lint check reports five expected warnings: one for the unfinished draft and four for unanswered questions in the vault's AGENTS.md. Fill in the draft's context, options and consequences, then approve it. If whykit is not found, run uv tool update-shell and open a new terminal.
Catch decision drift
Declare what each decision governs, then ask about any change, planned or committed:
whykit new --root my-ledger decision "Store money as integer cents" \
--owner Payments --status draft --source E-001 --applies-to 'src/payments/**' whykit affected --root my-ledger --files src/payments/ledger.py # before you edit whykit affected --root my-ledger --base origin/main --format markdown # in a pull request
Don't want to write scopes by hand? Let Git suggest them from the commits that changed each decision or name it in their message, then confirm:
whykit scope suggest --root my-ledger # preview
whykit scope suggest --root my-ledger --write # fill in decisions without a scope whykit scope check --root my-ledger --strict # in CI: fail when a scope points at code that moved
A source kept in the repository (a benchmark, a spec) counts too: when a pull request modifies it, every decision citing it is flagged.
Decisions about a library or a convention can watch for words instead of paths: with watch_terms: ["moment"], a change that adds import moment surfaces the "Use Luxon" decision. An agent can send its planned patch before applying it. We replayed real ADR repositories to tune this, and publish what did not work too.
Already have ADRs? Skip the vault and point it at the folder; scopes are inferred from the paths each ADR mentions, and moved code is flagged:
whykit affected --adr docs/decisions --base origin/main
The ten-minute tutorial goes from an empty repository to a flagged decision and its successor; every command in it runs in the test suite. Affected decisions covers scope patterns, every signal and a pull-request workflow.
Connect your agents
One command prints the MCP configuration for your host and adds a short, marked block to your code repository's CLAUDE.md or AGENTS.md telling the agent to look up decisions before it changes what they cover:
uv tool install --upgrade 'whykit[mcp]'
whykit connect --root my-ledger --host claude-code # preview whykit connect --root my-ledger --host claude-code --write # apply
Hosts: claude-code, cursor, vscode, codex, claude-desktop and generic. The server is read-only with eight tools (query, context, impact, status, pack, trace, backlinks, affected); records above your chosen sensitivity ceiling are never returned. The instruction block also tells the agent to call affected on the files it plans to change. whykit connect, whykit affected and the affected tool are new in 0.5.0; the MCP server itself is in 0.4.0. Read the agent guide.
Gate pull requests
Instructions ask; CI enforces. On a pull request, the GitHub Action fails when an accepted decision's reasoning is rewritten, a cited source is missing or a credential slips into the vault:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with: fetch-depth: 0
- uses: CometWeb-io/whykit@ with: root: decisions profile: ci affected: "true" # add the decisions this change touches to the job summary
See gate pull requests for the full workflow and a good and a bad example, and CI integration for PR comments, SARIF and other CI systems.
What would you like to do?
- See it on a real-looking vault: live Explorer demo of the payments example.
- Record a decision and change your mind later: record, check and supersede.
- Bring existing notes or ADRs: adopt existing Markdown.
- Browse the vault in a web UI: run the Explorer.
- Edit in Obsidian or your editor: Obsidian · language server.
- Review a changed source and share a filtered export: import, review and export.
Why WhyKit
| Plain ADRs | Wiki / Notion | WhyKit | |
|---|---|---|---|
| Lives next to the code, in Git | ✓ | ✓ | |
| Maps a code change to the decisions that govern it | ✓ | ||
| Flags decisions whose sources were retired, replaced or changed | ✓ | ||
| Review dates that expire and get reported | ✓ | ||
| Rewriting accepted decisions blocked in CI | ✓ | ||
| Read-only MCP access for agents, sensitivity-filtered | ✓ | ||
| Works offline, no account, no service | ✓ | ✓ |
Already happy with ADRs? Keep them; here is when they are the better fit. When you outgrow them, whykit adopt --profile adr-only brings them in.
Built to be trusted
- Plain files are canonical. Every view (queries, graphs, MCP, the Explorer) is derived from Markdown you can read and diff.
- Nothing phones home. No telemetry, accounts or network calls; a test breaks the socket layer and runs every vault command.
- A stable machine contract. Every
--jsonoutput has a published JSON Schema; error codes and exit codes are documented in the automation contract. - Tested hard. About 1,800 tests, property and fuzz tests for the parsers, reproducible builds, an SBOM and OpenSSF Scorecard on every release.
Limits, stated plainly
WhyKit checks that reasoning is cited, dated and not rewritten. It does not decide whether a source is true or a decision is right, and it does not re-check external sources on its own. Sensitivity labels filter what the MCP server and exports return; they are not access control, so keep real vaults in private repositories. whykit affected matches files by path, not by meaning, and sees only changes recorded in the vault. Agent instructions are a request: pair them with the CI gate. The project is a public alpha; see the feature status and the 0.4 upgrade guide.
Documentation
- Start here · Concepts · How-to guides · Connect agents · Affected decisions
- Command reference · Configuration · Lint rules
- CI integration · MCP server · Troubleshooting
- Example vaults: payments, tiny and Northline
Contributing
Issues and pull requests are welcome. Start with CONTRIBUTING.md; the whole suite runs offline with the standard library. If WhyKit is useful to you, a ⭐ helps other people find it.
Contributing · [Code of Conduct](C