All servers · Code & repositories · Research & knowledge

Meeba Brain

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

Measured by MCP Station

Description written by the publisher, not verified

Repository knowledge graph MCP server for codebase understanding and debugging.

Connect

claude mcp add --transport http meeba-brain https://meeba-context-mcp-469248886325.us-central1.run.app/mcp

{
  "mcpServers": {
    "meeba-brain": {
      "url": "https://meeba-context-mcp-469248886325.us-central1.run.app/mcp"
    }
  }
}

Tools as reported by the server

• 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.

Repository · JSON · Text for agents · Registry updated 2026-09-09