io.github.meemoprasadPublished by GitHub account meemoprasadv1.0.1Updated Oct 24, 2026
Repository knowledge graph MCP server for codebase understanding and debugging.
The publisher's own server: BrainDog
A remote MCP server that gives an AI assistant structural context about an indexed repository: symbols, callers, callees and dependencies.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.meemoprasad%2Fmeeba-brain/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"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.
Source: README.md at commit 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.
queryrequiredtop_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.
namerequiredEvery 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_namerequiredEvery 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_namerequiredWhat 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_pathrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
dog.brainOfficial publisher
BrainDog is a hosted record of projects, decisions and money that connected AI agents read before starting work and write their results into.
Published by GitHub account Nomannazir
Indexes a local or public git codebase so an assistant can search it, trace git history, check change impact and find stale docs, all with path:line citations.
Published by GitHub account zhang-liz
Gives an AI assistant memory of your professional network, stored as a graph in FalkorDB, so it can look up contacts, find people by topic, and save who you…
Published by GitHub account ara-5
Shared Graph-RAG memory for AI agents: markdown vault, wikilink recall, tasks, messaging.
Published by GitHub account make0-official
A local, offline memory server that lets Claude Code, Cursor, Codex and other MCP agents share one versioned store of durable facts.