Meeba Brain
Repository knowledge graph MCP server for codebase understanding and debugging.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Repository knowledge graph MCP server for codebase understanding and debugging.
Server tool list (5)
Raw names from tools/list. Only developers need these.
| search_code | 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. |
| get_symbol_definition | Finds 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. |
| get_callers | 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. |
| get_callees | 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. |
| get_dependencies | 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. |