Log inSubmit server
Koda logo

Koda

Agent-driven verification, reporting, project memory, and GitHub Actions workflow generation for coding projects.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Koda

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "koda": {
      "command": "npx",
      "args": [
        "-y",
        "koda-verify"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y koda-verify

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

The koda MCP server lets coding agents run focused verification, inspect reports, review recurring failures, and generate GitHub Actions workflows. It uses agent-supplied impact analysis for flows, endpoints, targets, commits, and flow limits, avoiding additional LLM analysis during MCP calls. Verification can combine read-only endpoint checks, integration tests, and scoped Kane browser flows for UI changes. Reach for it when an agent needs commit-level feedback and historical failure context without running every check on every change.

Use cases

  • Verify changed endpoints and tests after a commit
  • Run browser checks only for affected UI changes
  • Inspect recurring failures and previous fix history
  • Generate a validated GitHub Actions verification workflow

Key features

  • Agent-supplied impact analysis
  • Read-only endpoint verification
  • Scoped Kane browser flows
  • Integration test matching
  • JSON and Markdown reports
  • Persistent project memory

Tools4

What Koda lets your agent do. Expand a tool for its parameters.

Self-reported~112 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

13/13 checks healthy over the last 63d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 20h ago via OSV.dev · koda-verify (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads210Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Tools exposed4Callable tools this server registers over MCP.

How Koda works

What koda MCP server does

The koda MCP server provides a verification and memory layer for coding-agent workflows. It does not edit application code. Instead, it coordinates checks for a selected commit or change, writes machine-readable and human-readable reports, and records recurring failures and their resolution history.

Verification is scoped to the supplied impact analysis. An agent can identify relevant browser flows and endpoints after reading the code, then pass that information to Koda rather than asking another model to infer the impact. The resulting report includes verdicts, coverage information, evidence paths, risk data, and any action required.

How it works

Koda runs as a stdio MCP process started through the koda-verify package. The normal workflow is for an agent to edit and commit code, while Koda's hooks run verification in the background. The agent can then call the MCP tools to run focused checks or inspect the latest results.

Checks are selected according to changed files. API, configuration, and test-only changes can use endpoint checks and integration tests. UI-related changes can trigger headless Kane browser flows scoped to the affected pages or components. Endpoint verification uses GET, HEAD, and OPTIONS by default. Supported test runners include Jest, Vitest, Mocha, and node:test when tests match the changed files.

Each run produces JSON and Markdown files under .koda/reports/; browser session evidence is retained under .koda/evidence/. Project memory tracks stable failure keys, repeated patterns, passing fixes, and time to resolution. A skipped check, such as one affected by an offline application, is not treated as a failure or added to memory.

Setup and configuration

Install the package globally with npm install -g koda-verify, initialize a project with koda init, and use koda doctor to check Git, configuration, the target URL, directories, and Kane availability. The MCP process can be registered with a client using claude mcp add koda -- npx koda-verify mcp.

The koda MCP server uses the project's .koda directory for configuration, reports, evidence, and memory. Its target can be saved with koda target <url>, supplied for one run with --target, or set through KODA_TARGET. Target precedence is command-line flag, environment variable, project configuration, then automatic detection of common local development ports.

Browser verification is optional. Kane can be installed separately and authenticated with the user's own account. Without Kane, endpoint checks, integration tests, reports, and memory remain available while browser checks are marked SKIPPED.

Tools and capabilities

  • koda_verify runs focused verification using agent-provided flows, endpoints, target, commit, and max_flows values.
  • koda_report returns the latest full JSON report, including verdicts, coverage, and evidence paths.
  • koda_memory exposes recurring failures, fix confidence, and time-to-fix information.
  • koda_setup_cicd creates a validated GitHub Actions workflow.

The generated workflow can install dependencies, build when applicable, install and authenticate Kane through GitHub secrets, start the application, wait for its target, and run verification for the current commit. The template refuses to overwrite an existing workflow unless forced.

Limitations and notes

The koda MCP server supplies verification and reporting rather than code generation or code changes. Browser flows depend on Kane and the user's separate Kane authentication; no credentials are bundled. HTTP checks are read-only unless mutating methods are explicitly enabled and endpoints are declared by the agent.

Existing Git hooks are backed up before Koda appends its hooks, and the setup is designed to be idempotent. If an application is unavailable, Koda reports checks as skipped rather than failed. Groq is only a fallback for non-MCP impact analysis; MCP verification relies on the agent's supplied analysis.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Koda

koda is an MCP server that connects coding agents to a project's verification, reports, and memory workflow. Its main tools run focused checks, return the latest JSON report, expose recurring failure history, and generate a validated GitHub Actions workflow. Agents supply impact details such as flows, endpoints, target, commit, and flow limits.

Install it with `npm install -g koda-verify`, then register `npx koda-verify mcp` with your MCP client. In a project, run `koda init` to create `.koda`, install Git hooks, and detect an application target.

The agent supplies the affected flows and endpoints to `koda_verify`, along with the target, commit, and optional flow limit. Koda then matches checks to changed files, using endpoint checks and tests for many non-UI changes and browser flows for affected UI changes.

Yes. Register the stdio command `npx koda-verify mcp` through the client's MCP configuration.

Yes. Call `koda_setup_cicd`, or run `koda cicd`, to generate a validated workflow. It can install dependencies, build when present, start the app, wait for the target, authenticate Kane through GitHub secrets, and run Koda for the commit.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKoda AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/koda?style=directory)](https://allmcps.com/mcp/koda)
HTML Embed
<a href="https://allmcps.com/mcp/koda"><img src="https://allmcps.com/api/badge/koda?style=directory" alt="Koda on AllMCPs" /></a>