Meeba Brain

Repository knowledge graph MCP server for codebase understanding and debugging.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
96%
Integridad del esquema
100%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~919Tokens (definiciones de herramientas)
~1.1 KBTamaño de respuesta típico
Impacto moderado en la atención (0.72% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

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

Qué puede hacer

Inventario de herramientas

Herramientas (5)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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
}

Esquema de salida

{
  "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.

Esquema de entrada

{
  "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
}

Esquema de salida

{
  "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.

Esquema de entrada

{
  "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
}

Esquema de salida

{
  "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.

Esquema de entrada

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

Esquema de salida

{
  "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.

Esquema de entrada

{
  "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
}

Esquema de salida

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

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada5 herramientas
verificadoversión no registrada5 herramientas
verificadoversión no registrada5 herramientas