Repository knowledge graph MCP server for codebase understanding and debugging.
One address for any MCP client. No sign-in needed on this server.
5 read
Grouped by tool name. At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
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.