redcon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redcon_rankA | Rank repository files by relevance to a task. Call this FIRST on a new task, before grepping or reading: it returns the top-K paths with scores and reasons. Follow up with redcon_compress on the top hits. |
| redcon_overviewA | Lightweight repository map grouped by directory, filtered to the task's modules. Use to orient instead of ls -R or find; costs a few hundred tokens. For signatures, use redcon_repo_map. |
| redcon_compressA | Task-scoped compressed view of one file (signatures, imports and the relevant sections), typically 3-10x fewer tokens. Prefer this over reading a whole file; fetch the full file only if it is insufficient. |
| redcon_searchA | Regex search. scope='ranked' (default) limits matches to the task's relevant files; scope='all' covers the whole repo. Prefer over raw grep on large repositories. |
| redcon_budgetA | Plan how to fit a set of files under a token budget, choosing a compression strategy per file. Use before reading several files at once; returns per-file token costs, strategies, and which to drop. |
| redcon_structural_searchA | Search by AST pattern (ast-grep), not regex, so matches skip comments and strings. Needs ast-grep on PATH or redcon[ast_grep]; returns backend=unavailable otherwise so callers fall back to redcon_search. |
| redcon_repo_mapA | Repo map: top ranked files plus their class and function signatures with line numbers, under a token budget. Use for code structure across many files at once. Degrades to a path-only listing without the redcon[symbols] extra. |
| redcon_quality_checkA | Run a shell command, compress its output, and verify the compression against the M8 quality harness. Use instead of redcon_run when you want a structured pass/fail verdict on the compression. |
| redcon_runA | Run a shell command and return its output compressed for LLM consumption (pytest, git diff/status/log, builds, coverage and more). Use instead of a raw shell when output may exceed a screenful; token caps are hard and failures keep their essential detail. DISABLED by default; set REDCON_MCP_ENABLE_RUN=1 to enable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: repo_map provides ranked file signatures, overview gives directory grouping, rank prioritizes files, compress condenses a file, search and structural_search differ by regex vs AST, and budget plans token allocation. The only notable overlap is between redcon_run and redcon_quality_check, both of which run shell commands and compress output, but their verification approaches differ.
All tools share the redcon_ prefix and use snake_case, but the second part mixes nouns (repo_map, overview, budget) and verbs (rank, compress, search, run) without a consistent verb_noun pattern. This makes the API slightly less predictable, though still readable.
9 tools is well-scoped for a code exploration and compression server. Each tool covers a distinct phase of the workflow—ranking, mapping, searching, compressing, budgeting, and running commands—without unnecessary bloat or gaps.
The tool surface covers the core workflows: orientation (overview), relevance ranking (rank), structural mapping (repo_map), searching (search, structural_search), file compression (compress), budget planning (budget), and command execution (run, quality_check). A direct full-file read is absent, but that is intentional given the server's compression-focused design, so the gap is minor.