Senior Code MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_similar_codeA | Semantic search: embed Each result carries score + payload (path, name, kind, line range, docstring, text). |
| search_related_codeA | Structural search: expand the graph from Returns neighbor nodes (callers/callees/imports) with hop distance. Requires the repo to have been ingested (graph.json present). |
| ingest_repoA | Ingest a repo: parse, chunk, embed + upsert to Qdrant, build + save graph. Appends to the existing collection by default so multiple repos coexist;
pass |
| store_statsA | Return store stats: vector count (Qdrant) + node/edge counts (graph). |
| doctorA | Self-diagnose prerequisites before any org-facing setup. The onboarding agent calls this first to learn what is already healthy and what is missing, so it only asks the org about the things that actually need a human decision. Non-destructive: never writes, never creates a collection, never pulls a model. Checks:
Returns:
Per-check status (ok bool + detail) and an overall |
| search_contextA | Two-stage retrieval in one call: semantic search + graph expansion. Runs vector search for |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools are clearly distinct: search_similar_code handles semantic search, search_related_code handles graph-based structural search, and search_context combines both. ingest_repo, store_stats, and doctor cover ingestion, statistics, and diagnostics respectively, with no overlapping purposes.
Most tools follow a verb_noun pattern (search_context, search_related_code, ingest_repo, store_stats). The 'search_*' prefix is consistently used for search operations. The 'doctor' tool deviates by using a noun instead of a verb, but it is still recognizable and not chaotic.
With 6 tools, the set is well-scoped for a code comprehension server. Each tool serves a distinct and necessary function (ingest, search, stats, diagnostics), and the count is well within the optimal range.
The tool surface covers the full lifecycle for code search and understanding: ingestion with reset capability, multiple search modalities (semantic, structural, combined), statistics, and pre-flight diagnostics. No major gaps are apparent for the stated purpose.