Meeba Brain

Repository knowledge graph MCP server for codebase understanding and debugging.

我該用這個嗎

品質與安全性

A
說明品質
96%
結構描述完整度
100%
命名品質
100%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~919Token(工具定義)
~1.1 KB典型回應大小
中等的注意力影響(128k 上下文的 0.72%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

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

遠端端點

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

它能做什麼

工具清單

工具(5)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢search_code(query, top_k)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Natural-language or keyword description of what you're looking for."
    },
    "top_k": {
      "default": 8,
      "type": "integer",
      "description": "Max number of results to return (default 8, max 20)."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "x-fastmcp-wrap-result": true
}
🟢get_symbol_definition(name)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "The bare symbol name (e.g. \"get_upstream_impact\"), or\n\"ClassName.method_name\" for a specific method when the bare\nname is ambiguous across multiple classes."
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "x-fastmcp-wrap-result": true
}
🟢get_callers(function_name)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "function_name": {
      "type": "string",
      "description": "The bare function/method name (e.g. \"save_user\").\nIf multiple unrelated symbols share this name, results are\ngrouped by which definition they call."
    }
  },
  "required": [
    "function_name"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "x-fastmcp-wrap-result": true
}
🟢get_callees(function_name)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "function_name": {
      "type": "string",
      "description": "The bare function/method name (e.g. \"sync_repository\")."
    }
  },
  "required": [
    "function_name"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "x-fastmcp-wrap-result": true
}
🟢get_dependencies(file_path)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "file_path": {
      "type": "string",
      "description": "Repo-relative path (e.g. \"utils/knowledge_graph/graph_builder.py\").\nMatches by exact path first, then by suffix if no exact match\n(so \"graph_builder.py\" alone will still resolve if unambiguous)."
    }
  },
  "required": [
    "file_path"
  ],
  "additionalProperties": false
}

輸出結構描述

{
  "type": "object",
  "properties": {
    "result": {
      "type": "string"
    }
  },
  "required": [
    "result"
  ],
  "x-fastmcp-wrap-result": true
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本5 個工具
已驗證未記錄版本5 個工具
已驗證未記錄版本5 個工具