Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoGitHub token used by codna_fix with open_pr=true and codna_report_bug to interact with GitHub.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
codna_triageA

Understand a repository and locate the code relevant to an issue.

The sibling tools act, this one maps: codna_fix plans/acts on one bug and codna_recall retrieves stored code memory — triage is the zero-token map + suspect-file list you run first.

Requires the one-time free codna login device authorization (free community license); fully offline thereafter.

repo: a local path or a git URL (default: current directory). issue: optional description of what you're looking for. Returns suspect files + the context-reduction the engine achieved (0 LLM tokens).

codna_fixA

Find and fix a bug. Runs the full Codna agent + engine + risk simulation.

Requires the one-time free codna login device authorization (free community license) plus a provider key (BYOK — e.g. ANTHROPIC_API_KEY or codna key set anthropic). Offline truth: planning calls the provider API (network), and only open_pr=true writes to GitHub — codna_triage, codna_secure and codna_recall are the fully-offline tools.

Returns the root cause, confidence, model, and (when open_pr) the pull_request_url. Failures come back as 'codna_fix error: ...' text — the tool never raises.

codna_secureA

Prove which scanner findings are reachable. Ingests a SARIF 2.1.0 report (CodeQL / Semgrep / Snyk / Trivy), classifies each finding (exploitable / production-reachable / unreachable / unknown) via the local engine, and reports which are autofix-eligible. Read-only, deterministic, 0 LLM tokens — the SARIF file is the only input read; the repo is never scanned and the agent sidecar never starts.

sarif_path is REQUIRED (see the input schema) — there is no workspace scan or default-path fallback. SARIF provenance (tool name + revision) must be complete or the report is rejected. All failures come back as 'codna_secure error: ...' text — the tool never raises.

Requires the one-time free codna login device authorization (free community license); fully offline thereafter.

codna_recallA

Recall relevant code from the local on-device Telys memory — semantic + lexical search over the symbols this machine has already indexed, with zero LLM tokens and zero network calls.

Use when you need the code behind a concept ("where is SARIF provenance validated?") rather than a whole-repo map (codna_triage) — and when you want it offline. The index is built on first use (an empty index auto-indexes the repo, once) and is stored outside the git checkout. On a fresh machine, first use requires the one-time free codna login device authorization (free community license); the on-device memory runtime arrives via the login-gated runtime install. After that, recall is fully offline with no key and no network calls.

repo: a local path or git URL (default: current directory, or the server default set by codna mcp start --repo). query: what to recall (required — an empty query returns an error string). service: optional service name to scope recall to one service in a monorepo (default: all services). language: optional language filter such as "python" (default: all indexed languages). final_k: maximum number of symbols to return (default: 8). Returns matching symbols, the ranking explanation, and the candidate count as JSON. Failure modes (missing query, Telys memory not installed, unreadable repo) come back as "codna_recall error: ..." text — the tool never raises.

codna_report_bugA

File a report to thyn-ai/feedback — the public front door for algenta, codna, telys, and sqai. Files the same shape of issue codna report (the CLI) does. It only files the issue — codna_fix is the one that can open a PR with the fix.

Requires the one-time free codna login device authorization (free community license); auto-filing additionally needs a GitHub token (else a pre-filled URL).

title: a short summary, e.g. "codna fix hangs on a monorepo". body: what happened, or what you want — as much detail as you have. product: one of algenta, codna, telys, sqai, accounts, docs (default: codna). include_diagnostics: attach the same redacted output codna doctor prints — no secret values, only which config sources are set. Off by default. Returns the filed issue's URL, or — if it couldn't file automatically (no GitHub token reachable, offline) — a pre-filled URL for a human to finish submitting.

Prompts

Interactive templates invoked by user choice

NameDescription
fix_bugTemplated prompt: ask codna to locate then fix a bug.

Resources

Contextual data attached and managed by the client

NameDescription
capabilitiescodna's MCP capabilities — @-mentionable so the client knows what codna offers.

TDQS

A4.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a clearly distinct workflow: triage maps issues to suspect files, fix performs the actual bug fix, recall searches local code memory, secure classifies SARIF findings, and report_bug files feedback. There is minor conceptual overlap between triage and recall, but their descriptions draw a clear line between whole-repo mapping and concept-level symbol recall.

Naming Consistency4/5

All tools share the codna_ prefix and use lowercase imperative verbs, giving a predictable and recognizable pattern. The only small deviation is report_bug, which appends an object noun, while the others are bare verbs.

Tool Count5/5

Five tools is well-scoped for a coding-agent server: triage, fix, recall, secure, and bug reporting each cover a distinct high-level capability without redundancy. The count feels intentional rather than padded.

Completeness4/5

The toolset covers the main workflows an agent needs: locating relevant code, fixing bugs, recalling indexed symbols, verifying security findings, and reporting issues. Minor gaps exist such as no general issue-creation tool or explicit test/verify step, but these can be worked around via the CLI or GitHub.

Maintenance

ActivityMaintained
ResponsivenessNo issues