Meeba Brain

io.github.meemoprasad/meeba-brain · v1.0.1 · developer-tools

Meeba Brain is healthy: it completed an MCP handshake in 1910 ms and exposes 5 tools.

Repository knowledge graph MCP server for codebase understanding and debugging.

Endpoint: https://meeba-context-mcp-469248886325.us-central1.run.app/mcp (streamable-http)

Facts

Checked (UTC)	Status	Latency	Error
2026-10-15T05:55:41.998Z	Healthy	1910

`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_de
`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.