Codebase Brain MCP
Related Servers
Alternatives to Codebase Brain MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to build and query local repository memory, returning ranked files, context packs, relationship maps, semantic recall, and feedback-tuned search without uploading code.9270 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to index and search local files, websites, GitHub repos, and packages with hybrid AI-powered retrieval, all locally through IDE chat.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to search, retrieve, save, and sync encrypted Git-native context, transcripts, and takeaways across devices and contributors. It provides local full-text search, session access, and status tools while keeping context private on public repositories and avoiding token bloat.27 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search and query documentation from git repositories using hybrid search and structured metadata queries.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.56 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to find code by what it does rather than what it's called, searching local projects and remote GitHub or Bitbucket repositories all at once. Indexing and semantic search run fully offline with a locally loaded model, so code never leaves the machine.164 PyPIApache 2.0
TDQS
Scored across 9 tools
Each tool has a clearly distinct role: indexing, targeted search, prose Q&A, history explanation, impact analysis, doc drift, commit-message search, line reading, and repo listing. The descriptions explicitly route agents between overlapping-sounding tools, such as search vs. ask_codebase and explain_history vs. search_history.
Most tools follow a clear verb_noun pattern: index_repo, ask_codebase, explain_history, find_doc_drift, search_history, read_lines, list_repos. Minor deviations are the bare search and noun-phrase impact_of_change, but the set remains predictable and readable.
Nine tools is well-scoped for a codebase indexing and intelligence server. Each tool covers a meaningful operation without obvious redundancy or bloat.
The surface covers indexing, discovery, search, Q&A, history, impact analysis, doc drift, and exact file reading, which supports the core workflows. Minor lifecycle gaps remain, such as no explicit repo removal or unindex operation, but agents can work around them.