Codna connects an AI assistant to Codna’s repository tools through the Model Context Protocol. Running as a local server, it exposes tools for understanding a codebase, investigating a reported bug, reviewing security scanner findings, recalling relevant code, and sending feedback to the project. This lets someone work with Codna from a supported MCP client rather than switching exclusively to the command line. The tools have different requirements and effects: several are read-only, while opening a pull request or filing a report can write to GitHub.
What can Codna do?
Codna exposes five tools. Repository triage maps a repository and identifies files relevant to an issue; it is deterministic, read-only, and uses zero model tokens. The fix tool analyzes a bug and returns a fix plan by default. It can open a pull request when supplied with a Git URL and a GitHub write token.
- Classify SARIF scanner findings by reachability and report autofix eligibility.
- Search code in local on-device memory without calling a model or changing the repository.
- File a bug, feature request, or question to the project’s public feedback GitHub repository.
The security tool requires a SARIF file with complete provenance. It classifies and reports findings; remediation is performed through Codna CLI commands, not through that MCP tool. The feedback tool can return a pre-filled issue link when it lacks a suitable token for automatic submission.
How Codna connects and authenticates
The documented MCP server runs locally over stdio, with the MCP client starting it as a child process. The guide names Cursor and Claude Desktop and also documents use with another MCP client. There is no hosted MCP endpoint documented in the reviewed guide. Executing any tool requires one-time free Codna device authorization; listing tools and initialization are credential-free. The fix tool additionally needs a model-provider key, and automatic GitHub submissions require a GitHub token. MCP support is an optional install extra, not part of the base Codna package.
Who is Codna best for?
Codna suits developers who want repository triage, fix planning, security finding analysis, code recall, or project feedback available inside an MCP client. Its verified individual plan is Free and includes the MCP server. Users need free Codna device authorization to execute tools. Fix analysis also needs a provider key, with charges billed by that provider; Codna’s pricing page lists the MCP server under its free individual plan.
What Codna can access and change
Repository mapping and recall run locally; for model-assisted fixes, Codna sends an issue-specific evidence bundle to the selected provider, and secret redaction is always on. Triage, security classification, and recall are read-only. The fix tool does not apply its plan to a local checkout, but can open a pull request when given a Git URL and write-capable GitHub token. The feedback tool can create a real issue in the project’s public GitHub repository when authorized. Without a suitable token, it returns a pre-filled issue link instead.
Alternatives to Codna
For adjacent repository and developer workflows, GitHub Official MCP Server connects an assistant to GitHub, while Supabase MCP Server connects one to Supabase projects. These are alternatives to consider when the task centers on interacting with those services rather than Codna’s documented repository triage, fix planning, security classification, local recall, and feedback tools.
