Koda

Name: Koda
Author: aabxtract

by aabxtractversion 0.3.2i★ –iRuns on your computer

Registry nameio.github.aabxtract/koda

Install

Overview

Description from the maker (original English)

Verification and memory layer for coding-agent workflows.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "koda": {
      "command": "npx",
      "args": [
        "-y",
        "koda-verify"
      ]
    }
  }
}

Run this in your terminal

claude mcp add koda -- npx -y koda-verify

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "koda": {
      "command": "npx",
      "args": [
        "-y",
        "koda-verify"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "koda": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "koda-verify"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account aabxtract, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– 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

Compared with others in Search & AI memoryi

More stars than 0% of the other 7254 servers in this category
Published to the registry more recently than 35% of the other 7254 servers in this category
Basic checks equal to or better than 100% of the other 7254 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 Koda safe?

It passed 1 of 1 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 –, and the latest version (0.3.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

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.

Koda

Verification and memory for coding-agent workflows. Install once, verify the changes that matter, remember what keeps breaking.

1,000+ downloads on Open VSX — Koda is already watching commits in editors around the world.


npm	`npm install -g koda-verify` (npmjs.com)
IDE	Open VSX — works in VS Code, Cursor, Windsurf, VSCodium
MCP	Registry
Landing	aabxtract.github.io/koda

Why Koda exists

Coding agents write features in minutes — but who verifies every commit? Full test suites are too slow to run per commit, so most verification happens late (or never). Koda closes that gap: on every commit it verifies only what changed, in seconds-to-minutes, and remembers what keeps breaking so your agent stops reintroducing old bugs.

Koda never writes code. It orchestrates verification, remembers patterns, and reports — to both the human and the agent.

The three surfaces

Surface	Responsibility	Activation
Core + CLI	Verification, reports, memory, git hooks, CI generation	`koda init`, `koda run`
MCP server	Agents call `koda_verify` / `koda_report` / `koda_memory` / `koda_setup_cicd`	MCP client configuration
IDE extension	Ambient status bar, report viewer, one-click enable, Git watching	User clicks Enable

How it works — the pipeline

git commit

│ ▼ pre-commit ── secret guard (blocks committed API keys / private keys) │ ▼ post-commit ── koda run (background, never blocks you) │ ▼

Read diff ──────────── classify files: api / page / component / lib / config / test
Impact analysis ────── agent-supplied (MCP) → Groq fallback → deterministic heuristics
Kane browser flows ─── headless, scoped to changed UI only (page/component changes)
Endpoint checks ────── GET / HEAD / OPTIONS only; regressions flagged (200 → 500)
Integration tests ──── Jest / Vitest / Mocha / node:test, matched to changed files
Report ─────────────── JSON (agent-readable) + Markdown (human-readable)
Memory ─────────────── recurring patterns, resolution history, time-to-fix

Most commits never launch a browser: API/config/test-only changes verify with endpoints + tests in seconds. Browser flows fire only when UI files change.

Quick start

npm install -g koda-verify

cd your-project koda init # creates .koda/, installs git hooks, detects your app's port koda doctor # verifies: git, config, Kane CLI, target URL, directories

Then just keep committing — verification runs in the background on every commit.

One-time browser setup (optional, per user)

Browser flows are powered by the Kane CLI. The IDE extension onboards it for you: click *Enable* and Koda offers to install Kane and connect your account. Or do it manually:

npm install -g @testmuai/kane-cli

kane-cli login --oauth # opens your browser — use (or create) YOUR OWN Kane account

About Kane accounts — yours, not ours

Koda ships zero credentials. Every Koda user authenticates their own Kane account:

The extension's OAuth flow opens the Kane login in *your* browser; new users register there
Your session lives locally in ~/.testmuai/ on your machine — never synced, never proxied
Browser-flow credits come from *your* Kane account, not the developer's
In CI, each repo configures its own KANE_USERNAME / KODA_ACCESS_KEY-style secrets

No Kane? No problem. Koda runs in degraded mode: endpoint checks, integration tests, memory, and reports all work; browser flows are honestly marked SKIPPED — never faked.

Target URLs — localhost, LAN, or hosted

Koda verifies whatever your app points at. The default is auto-detected at koda init (probes common dev ports: 3000, 5173, 8080, 8000, 4200, 5000…). Override it three ways:

koda target https://myapp.vercel.app      # permanent — hosted URL, https auto-detected

koda target 192.168.1.5:8080 # LAN IP, http auto-detected koda run --target https://preview-123.example.com # one-off run KODA_TARGET=https://staging.example.com # per-session / CI via env

Precedence: --target flag → KODA_TARGET env → .koda/config.json → auto-detected default.

CLI reference

Command	What it does
`koda init [--force]`	Create `.koda/`, install non-destructive git hooks, detect target
`koda run [--project ] [--commit ] [--target ] [--max-flows ]`	Verify a commit now
`koda report`	Show the latest report
`koda memory`	Dump project memory (patterns, history, fixes)
`koda target`	Validate, save, and health-check a new target URL
`koda cicd [--force]`	Generate a validated GitHub Actions workflow (refuses overwrite)
`koda doctor [--kane]`	Environment check; `--kane` empirically probes the Kane schema
`koda mcp`	Start the MCP server (stdio)

Agent integration (MCP)

claude mcp add koda -- npx koda-verify mcp

Works with any MCP client: Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Zed. In a development checkout: claude mcp add koda node /absolute/path/to/koda/mcp/server.js.

MCP tools

Tool	Purpose
`koda_verify`	Run focused verification. The agent supplies its own impact analysis (`flows`, `endpoints`, `target`, `commit`, `max_flows`) — it already read your code, so no LLM cost and no guessing. Groq is only a fallback for non-MCP runs
`koda_report`	Latest full JSON report — verdicts, coverage, evidence paths
`koda_memory`	Project memory — recurring failures, fix confidence, time-to-fix
`koda_setup_cicd`	Generate a validated GitHub Actions workflow

The agent loop

agent edits code → commits → hook fires koda run → report written

→ agent calls koda_verify (its own flows) / koda_report via MCP → reads the verdict → fixes what failed → commits again → memory marks the failure RESOLVED (with time-to-fix recorded)

Reports record analysis_source: 'agent' when the agent supplied flows — verifiable proof the loop is agent-driven.

Reports

Every run writes a timestamped pair to .koda/reports/:

.koda/reports/2026-08-30T14-35-28-909Z-9416b29.json   ← agent-readable

.koda/reports/2026-08-30T14-35-28-909Z-9416b29.md ← human-readable

The JSON includes: commit metadata, analysis_source (agent / llm-fallback / fallback), risk level, per-check results with evidence file paths, memory context (similar failures, patterns, fix confidence), and action_required with priority and suggested focus. Markdown renders PASS / FAIL / SKIPPED distinctly with coverage status.

Raw Kane session events are preserved per-flow under .koda/evidence/.

Memory — remembers what keeps breaking

Every failed check gets a stable key; failures that recur 2+ times become patterns
When a fix lands and the check passes, the failure is marked resolved with time_to_fix_ms
Coverage-gap findings ("no tests cover app/page.js") resolve automatically once a passing test covers those files
Skipped checks (app offline) never pollute memory
Writes are atomic; corrupt memory files are quarantined, not deleted

Safety guarantees

Non-destructive hooks — existing pre-commit/post-commit/pre-push hooks are backed up before appending; Husky respected; idempotent via marker
Read-only HTTP by default — only GET / HEAD / OPTIONS; mutating methods require explicit opt-in (allow_mutating_methods: true) plus agent-declared endpoints
Honest results — if the app is down, checks are SKIPPED, never reported as failures; skipped checks never enter memory
No secrets shipped — the package contains zero credentials; the pre-commit guard blocks accidentally committed keys

CI/CD

koda cicd

Generates .github/workflows/koda.yml from a validated template: Node setup, npm ci, build-if-present, Kane CLI install + auth via GitHub secrets (KANE_USERNAME, KANE_ACCESS_KEY), app start, wait-on target, koda run --commit ${{ github.sha }}. Template-first — no LLM-generated YAML. Refuses to overwrite without --force.

Configuration reference (`.koda/config.json`)

"kane": { "target": "http://localhost:3000", "headless": true, "max_steps": 30, "timeout_ms": 300000 }, "tests": { "browser_flows": true, "endpoint_tests": true, "integration_tests": true, "allow_mutating_methods": false, "expected_statuses": { "GET /api/health": [200] } }, "notify": { "telegram": false, "discord": false } }

Environment variables

Optional — Koda works without any of these. Loaded from the project .env, falling back to ~/.koda/.env (configure once, use everywhere):

GROQ_API_KEY=        # Groq fallback impact analysis (agent runs skip this entirely)

KODA_TARGET= # override target URL (flag > env > config) KODA_TEST_TOKEN= # bearer token for authenticated endpoint checks KODA_PROJECT= # default project path for CLI/MCP TELEGRAM_BOT_TOKEN= # notifications TELEGRAM_CHAT_ID= DISCORD_WEBHOOK_URL=

Development

npm install

npm run check # syntax-check all sources npm test # node:test suite npm link # local koda binary for development

See koda-v3-build-guide.md for the full implementation contract.

License

MIT

Koda

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Koda

Why Koda exists

The three surfaces

How it works — the pipeline

Quick start

One-time browser setup (optional, per user)

About Kane accounts — yours, not ours

Target URLs — localhost, LAN, or hosted

CLI reference

Agent integration (MCP)

MCP tools

The agent loop

Reports

Memory — remembers what keeps breaking

Safety guarantees

CI/CD

Configuration reference (.koda/config.json)

Environment variables

Development

License

Configuration reference (`.koda/config.json`)