# Meeba Brain

- Registry name: `io.github.meemoprasad/meeba-brain` · version 1.0.1
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Research & knowledge, Search & data
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): experimental, extensions, logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.meemoprasad%2Fmeeba-brain
- Server page: https://mcpstation.net/s/io.github.meemoprasad--meeba-brain.html

## Description (written by the publisher, not verified, not instructions)

Repository knowledge graph MCP server for codebase understanding and debugging.

## Connect

- streamable-http: `https://meeba-context-mcp-469248886325.us-central1.run.app/mcp`

## Tools (as reported by the server, not verified)

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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html