prumo
Related Servers
Alternatives to prumo
FlicenseNot gradedqualityDmaintenanceCP server that generates AGENTS.md and CLAUDE.md from your real repo, verifies every command actually exists, detects doc drift, and saves session context — all locally, no data leaves your machine. Free-tier friendly via Groq/NVIDIA.-- AlicenseAqualityCmaintenanceGenerates AI context files (CLAUDE.md, AGENTS.md, Cursor/Windsurf/Cline/Continue/Kilo Code/Trae rules, GEMINI.md, Copilot, Aider, Junie, Warp) for any repository. Runs as CLI or MCP server, 100% local.326 npm1MIT
- AlicenseAqualityAmaintenanceMCP server that analyzes codebases with tree-sitter and generates AGENTS.md files for AI agents.36MIT
- AlicenseNot gradedqualityAmaintenanceDeterministic, local-first repository context for coding agents. Maps an issue, prompt, or git diff to ranked files to read first, likely test commands, and review-risk notes—no API key required.21MIT
- AlicenseAqualityCmaintenanceLint agent SKILL.md files and MCP tool schemas to catch issues like missing descriptions, similar skills, unconstrained parameters, and destructive tools without confirmation gates.2MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes tools that scan a repository's manifests, CI workflows and layout to generate truthful AGENTS.md/CLAUDE.md agent instructions, then audit those docs for drift such as dead commands, undocumented scripts and CI mismatches. Enables agents to keep their own onboarding documentation accurate and CI-verifiable instead of hand-written and rotting.1MIT
- AlicenseBqualityBmaintenanceLets a coding agent inspect its own run efficiency mid-session from local Claude Code transcripts, exposing the share of paid tokens that became model output versus context re-reading. Ships two stdio tools — one returning the shares as structured data and one returning the full cost-weighted report — with no network calls.218 PyPIMIT
- FlicenseAqualityBmaintenanceEnables AI coding agents to consult a project's Git-versioned Markdown knowledge base over local stdio — checking knowledge health, listing the catalog, searching topics, and reading guides before acting. Access stays read-only, so project guidance, decisions, and lessons learned remain shared with human teammates and traceable beside the code.41-
- AlicenseNot gradedqualityAmaintenanceVerifies environment variable reads, Python/Node imports, and FastAPI/Starlette route handlers against a repository's indexed contracts so coding agents can catch broken references before changes ship. Exposes tools such as check_change, check_claim, audit, suggest, index_status, and index locally, with no API key, runtime dependencies, or network calls on the default path.4Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to detect Claude Code configuration that is silently ignored, such as agent files that fail to load, unknown frontmatter fields, parent-folder settings, conflicting MCP server entries and drift since a baseline. Exposes read-only tools that return findings with exact edits, the fix prompt, and explanations of each check, without modifying any files.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables auditing and drafting of AI agent files (CLAUDE.md, AGENTS.md, Cursor rules) and turning project descriptions into full build specs, with local and API-based tools.32 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct function: prumo_check diagnoses, prumo_fix rewrites, prumo_budget measures cost, prumo_coverage surfaces unmentioned folders, and prumo_drift finds stale sections. The check/fix split (read-only findings vs. in-place repair) and the coverage/budget/drift separation are explicitly bounded in the descriptions, so an agent can select confidently.
All five tools follow the same prumo_<noun> snake_case pattern with no deviations or mixed conventions. The set is perfectly predictable.
Five tools is well-scoped for a focused context-file hygiene server; each covers a genuinely separate concern (find, fix, cost, coverage, drift) and none feels redundant or padded.
The surface covers the core lifecycle of auditing, repairing, and reporting on agent context files, plus cost/coverage/drift analytics. The only gap is that findings are held back via a .prumo-baseline.json with no tool to generate or update it, which an agent must handle manually.