Skip to content

Meeba Brain

by meemoprasad · remote · no sign-in to list tools · v1.0.1 · published by GitHub user meemoprasad

Repository knowledge graph MCP server for codebase understanding and debugging.

Read only
CompareRegistry entry

5 tools: 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Only reads 5Claude Code: allow
  • get_calleesEvery function/method the given function calls -- what it depends on to do its job.No findings

    Why it is in this group

    • The name "get_callees" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_callersEvery place in this repo that calls the given function or method -- a COMPLETE list from the parsed call graph, not a best-effort guess.No findings

    Why it is in this group

    • The name "get_callers" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_dependenciesWhat a specific file imports/depends on.No findings

    Why it is in this group

    • The name "get_dependencies" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_symbol_definitionFinds 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).No findings

    Why it is in this group

    • The name "get_symbol_definition" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • search_codeHybrid semantic + keyword search over the connected repository's actual indexed content.No findings

    Why it is in this group

    • The name "search_code" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__meeba-brain__search_code",
      "mcp__meeba-brain__get_symbol_definition",
      "mcp__meeba-brain__get_callers",
      "mcp__meeba-brain__get_callees",
      "mcp__meeba-brain__get_dependencies"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as meeba-brain. Review it before you use it.