agents-md-generator
Related Servers
Alternatives to agents-md-generator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that provides AI coding agents automatic access to AGENTS.md documentation from GitHub repositories, enabling understanding of codebase conventions and patterns.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.46 npm4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to navigate and understand codebases through file descriptions, semantic search, and code recommendations without repeatedly scanning files.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that indexes your codebase using tree-sitter AST parsing and gives AI tools instant access to structural intelligence like dependency graphs, call trees, and dead code detection from a local SQLite database.MIT
- AlicenseAqualityBmaintenanceMCP server that helps AI coding agents understand a repository by providing lightweight tree/map, code search, and token-budgeted context packing tools without dumping the entire monorepo into the prompt.32 npm105MIT
- AlicenseAqualityBmaintenanceAn MCP server that generates ranked, token-budgeted code structure maps using Tree-sitter AST analysis and PageRank, enabling AI agents to quickly understand unfamiliar codebases.234 npmMIT
TDQS
Scored across 3 tools
The three tools have distinct roles: scan_codebase produces the payload, read_payload_chunk retrieves it, and generate_agents_md orchestrates. scan_codebase and generate_agents_md could initially look similar since both relate to codebase analysis, but the descriptions explicitly delineate when to use each, resolving the ambiguity well.
All names use snake_case with a verb-first convention (scan_codebase, generate_agents_md, read_payload_chunk), which is predictable and readable. read_payload_chunk adds an extra noun qualifier relative to the others, a minor deviation from a strict verb_noun pattern.
Three tools is slightly thin, but each earns its place in a narrow, well-defined workflow (scan → read → generate). There is no obvious redundancy, and the count matches the focused purpose of AGENTS.md generation.
The surface covers the full generation lifecycle: scanning with cache control, chunked payload retrieval, and a create-or-update orchestrator that also feeds the writing rules. Minor gaps exist (no explicit validation or standalone cache-management tool), but agents can complete the core workflow.