agent-context-router
Related Servers
Alternatives to agent-context-router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to fetch, search, and retrieve markdown content from remote Git repositories. Supports both public and private repositories with authentication, allowing AI assistants to access documentation and notes stored in Git.MIT

RepoPrimerofficial
AlicenseAqualityDmaintenanceProvides fresh project context to coding agents by combining Markdown documentation and live Git state, enabling deterministic startup briefs and bounded document retrieval for MCP-compatible tools.44 npmApache 2.0- AlicenseNot gradedqualityDmaintenanceServes markdown instructions as tools to provide LLMs with team playbooks, coding standards, domain knowledge, and personal workflows through version-controlled files.5 npmMIT
- AlicenseAqualityCmaintenanceEnables agents to search, read, list, and amend a git-backed markdown knowledge base, automatically committing and publishing changes.4MIT
- AlicenseBqualityDmaintenanceEnables AI agents to read git commits from local repositories and generate beautifully formatted, categorized changelogs.23 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, create, patch, lint, and synchronize a shared Markdown+git knowledge base across multiple machines and sessions, with confidence metadata and protocol resources.1MIT
TDQS
Scored across 3 tools
The three tools cover distinct retrieval modes: full enumeration (list_modules), keyed fetch (load_module), and fuzzy discovery (search_context). The descriptions explicitly disambiguate the two discovery paths — list is for trigger-based lookup, search is the fallback when no trigger matches — so an agent can pick correctly.
All three names follow a consistent verb_noun snake_case pattern (list_modules, load_module, search_context). The verbs are semantically meaningful and map cleanly onto the action each tool performs.
Three tools is on the thin side but each earns its place in a discover-load-search workflow. Nothing redundant is present, though the surface is small enough that a single missing operation would be noticeable.
The surface covers the full read lifecycle: enumerate modules, fuzzy-find one, and load its text. Minor gaps exist — no way to unload/release a loaded module or check version/freshness of the policy corpus — but these are workarounds an agent can live without.