memorepo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | GitHub token used to sign in and access the repositories you want to index. Can be configured in the .env file instead of signing in with GitHub when prompted. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_space_repositoriesA | List compact repositories and project names for this MemoRepo space. Branches and detailed metadata are omitted unless explicitly requested. |
| snapshot_index_coverageC | Report verified source-integrity coverage for the immutable snapshot by project and file extension, including reported skips, exclusions, quality, and whether the inventory is exhaustive. Candidate files are not claimed as proven CBM graph membership. |
| list_snapshot_filesA | List regular files captured in one repository's immutable snapshot tree. Use this for file inventories and extension/path existence questions; results contain relative paths only and support prefix/glob filtering plus offset pagination. |
| read_snapshot_fileA | Read bounded numbered UTF-8 lines from a regular file in one immutable repository snapshot, with digest and truncation metadata. |
| search_snapshot_textB | Search literal text across immutable snapshot files, including files CBM does not index. Paginate to has_more=false and require complete=true before absence conclusions. |
| list_projectsA | List CBM projects available inside this MemoRepo space snapshot. |
| index_statusB | Check CBM indexing status for this space snapshot or one project inside it. |
| get_architectureC | Return the native CBM architecture summary for this space snapshot, or one project when project is provided. |
| get_graph_schemaC | Return native CBM graph schema details for this space snapshot. |
| search_graphC | Run native CBM structured graph search within this space snapshot. |
| search_codeC | Run native CBM indexed code text search within this space snapshot. Use offset and has_more for pagination; requested limits above 25 use an effective limit of 25. Scoped searches expose the engine's first 250 matches; cross-project searches can page across the combined accessible matches. |
| trace_pathC | Trace a uniquely resolved function or method. Includes USAGE references for callbacks and functions passed as values. |
| get_code_snippetC | Run native CBM snippet lookup by qualified symbol name. |
| query_graphA | Run the supported read-only Cypher subset against this space snapshot. max_rows must be between 1 and 25 and is a global limit for projectless calls. Use offset for scoped pagination. |
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 14 tools
Most tools have clearly separated roles: snapshot filesystem access (list_snapshot_files, read_snapshot_file, search_snapshot_text) versus CBM code-graph access (search_graph, trace_path, get_code_snippet, query_graph). The fuzziest boundaries are search_snapshot_text vs search_code (literal text across all files vs indexed code text) and list_space_repositories vs list_projects, but the descriptions explicitly draw these distinctions. An agent can pick correctly with careful reading, though the two search tools could still be misselected.
Nearly all tools follow a verb_noun convention (list_snapshot_files, read_snapshot_file, search_snapshot_text, get_architecture, trace_path, search_code), with snapshot tools consistently prefixed by 'snapshot'/'space'. The exceptions are snapshot_index_coverage and index_status, which are noun phrases rather than verb-led, plus a mild inconsistency between 'get_' and 'search_'/'query_' retrieval verbs.
Fourteen tools is well within a reasonable range and splits cleanly into two coherent surface layers (five snapshot-integrity tools, nine code-graph tools). Each tool corresponds to a distinct operation with no filler or duplicated capability, so the count is well matched to the server's dual purpose.
The read-only surface covers inventory, coverage reporting, file reading, literal search, project listing, indexing status, architecture, schema, graph search, path tracing, snippet lookup, and a Cypher escape hatch — a solid lifecycle for inspecting a code snapshot. Minor gaps remain: there is no way to enumerate snapshots/versions or diff two snapshots, and symbol-reference discovery depends on trace_path rather than a dedicated callers/callees tool.