Skip to main content
Glama

Server Details

Repository knowledge graph MCP server for codebase understanding and debugging.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
meemoprasad/meeba-brain-marketplace
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of code understanding: callees (outgoing calls), callers (incoming calls), dependencies (imports), symbol definitions (location/signature), and open-ended search. There is no overlap between them; search_code is explicitly positioned as the fallback for when exact symbols aren't known.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_callees, get_callers, get_dependencies, get_symbol_definition, search_code. 'search_code' uses 'search' as the verb, matching the same structure. No camelCase or mixed conventions.

Tool Count5/5

Five tools is a well-scoped set for a code-intelligence server. Each tool covers a necessary query type without redundancy, and the count avoids the confusion of a large surface while being substantial enough to handle common codebase exploration tasks.

Completeness4/5

The set covers the main code navigation needs: caller/callee graphs, file dependencies, symbol definitions, and free-text search. Minor gaps exist, such as lacking direct file-content retrieval or type hierarchy queries, but these are often handled by search_code or are out of scope for a 'brain' server focused on relationships and definitions.

Available Tools

5 tools
get_calleesA
Read-onlyIdempotent
Inspect

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.

Inputs: function_name (required). Returns: result

get_callersA
Read-onlyIdempotent
Inspect

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.

Inputs: function_name (required). Returns: result

get_dependenciesA
Read-onlyIdempotent
Inspect

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.

Inputs: file_path (required). Returns: result

get_symbol_definitionA
Read-onlyIdempotent
Inspect

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.

Inputs: name (required). Returns: result

search_codeA
Read-onlyIdempotent
Inspect

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.

Inputs: query (required), top_k. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.