io.github.meemoprasad由 GitHub 账号 meemoprasad 发布v1.0.1更新于 Oct 24, 2026
Repository knowledge graph MCP server for codebase understanding and debugging.
发布方自己的服务：BrainDog
一个远程 MCP 服务器，为 AI 助手提供已索引代码库的结构化上下文：符号、调用方、被调用方和依赖关系。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.meemoprasad%2Fmeeba-brain/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"meeba-brain": {
"type": "http",
"url": "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
}
}
}Give your AI coding assistant a structural understanding of your codebase.
Meeba Brain MCP connects Cursor to Meeba Brain's repository knowledge graph, helping it understand how functions, files, services, and dependencies are connected.
Instead of relying only on text search, Cursor can use Meeba Brain's structural context to investigate unfamiliar code, trace relationships, and reason about changes with better grounding.
Text search helps you find where a name or phrase appears.
A knowledge graph helps you understand how the code is connected.
For example, instead of only finding refundOrder, you can investigate:
The difference is not simply finding more text. It is understanding the relationships between the code.
When debugging, the file showing the error is not always the file causing the problem.
A bug may involve several connected components:
API route → service → worker → dependency
Without understanding those relationships, an AI assistant may suggest a plausible fix that changes the wrong layer or misses an affected caller.
Meeba Brain provides Cursor with repository-grounded structural context so Cursor can investigate the relevant relationships before proposing a change.
This helps Cursor identify the relevant code, understand potential impact, and propose better-informed fixes.
Meeba Brain does not guarantee that every fix is correct. Its purpose is to give Cursor better evidence and structural context for reaching the right fix.
Meeba Brain MCP provides access to repository knowledge graph capabilities, including:
Meeba Brain MCP requires a connected, indexed repository.
The repository is connected and indexed on Meeba Brain, not inside Cursor.
Go to:
After signing in, connect the repository you want to investigate on Meeba Brain.
Meeba Brain needs to build the repository's structural knowledge graph.
Wait until indexing is complete before connecting the MCP to Cursor.
Open the MCP connection page:
https://meeba.ai/brain/connect
Enable MCP and copy the key provided by Meeba Brain.
Keep this key private.
In Cursor:
Use the exact server URL and authentication header shown in Meeba Brain.
After saving the configuration, open the MCP settings and make sure Meeba Brain is enabled.
Open your repository in Cursor and ask a question such as:
"Which services call refundOrder()?"
"Explain how this feature flows through the codebase."
"What could be affected if I change this API?"
"Trace the code flow from this route to the implementation."
"Why is this function being called?"
Start with one real function, dependency, or bug you want to understand.
Meeba Brain MCP is not a replacement for Cursor.
It is a repository knowledge graph integration that gives Cursor additional structural context.
Cursor remains responsible for the coding conversation, reasoning, and code changes.
Meeba Brain provides the repository intelligence that helps make that reasoning more grounded.
Learn about Meeba Brain:
Connect your repository and enable MCP:
https://meeba.ai/brain/connect
Understand the relationships. Investigate the evidence. Make better-informed changes.
来源：README.md，提交 406680a
Hybrid semantic + keyword search over the connected repository's actual indexed content. Use this for open-ended questions ("where is rate limiting implemented?", "how are uploads validated?") where you don't already know an exact symbol or file name -- for those, use get_symbol_definition or get_dependencies instead, they're more precise.
query必填top_kFinds where a function, class, or method is actually defined in this repo -- exact file, line range, and signature-relevant metadata (async, decorators, docstring if present). Use this before assuming a symbol's location/signature from memory or from a similarly-named symbol in a different file.
name必填Every place in this repo that calls the given function or method -- a COMPLETE list from the parsed call graph, not a best-effort guess. Use this before renaming/changing a function's signature, or when you need to understand a function's blast radius before modifying it.
function_name必填Every function/method the given function calls -- what it depends on to do its job. Use this to understand a function's behavior by seeing what it delegates to, before assuming what it does from its name alone.
function_name必填What a specific file imports/depends on. Use this to understand a file's place in the codebase before assuming what's available to it, or before moving/refactoring it.
file_path必填已满足适用检查项的 90%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请在仓库或注册中心条目中声明许可证。
dog.brain官方发布者
BrainDog 是一个托管记录库，集中保存项目、决策与资金，接入的 AI 代理在开工前读取、结束后写入。
由 GitHub 账号 Nomannazir 发布
为本地或公开 git 代码库建立索引，让助手能检索代码、追溯 git 历史、分析改动影响并发现过期文档，结果均带路径与行号引用。
由 GitHub 账号 zhang-liz 发布
为 AI 助手提供职业人脉记忆，数据以图的形式存放在 FalkorDB 中，可查询联系人、按话题找人并记录你见过的人。
由 GitHub 账号 ara-5 发布
面向AI智能体的共享Graph-RAG记忆：markdown vault、wikilink召回、任务、消息传递。AI 翻译
由 GitHub 账号 make0-official 发布
本地离线的记忆服务器，让 Claude Code、Cursor、Codex 等 MCP 代理共享同一份带版本记录的持久事实库。