localscope-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCALSCOPE_PORT | No | Port for the HTTP server when transport is http. Default is 3000. | 3000 |
| LOCALSCOPE_RG_PATH | No | Path to ripgrep binary, if you have one. Auto-detected if not set. | |
| LOCALSCOPE_TRANSPORT | No | Transport mode for the MCP server. Defaults to 'stdio'. Set to 'http' to enable HTTP mode. | stdio |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| localscope_indexA | Build a local, private index of a repository: files, symbols (functions/classes/types), import graph, and optional embeddings. Zero network calls — the index never leaves the machine. Args:
Returns: File/chunk/symbol counts, embedder mode (onnx or lexical), duration. Use when: the user asks to index/analyze the codebase, or before localscope_search / localscope_impact on a repo not indexed yet in this session. |
| localscope_searchA | Search the local index for code or docs by meaning, symbol name, or fragment. Combines embeddings (if installed) with lexical identifier matching — all offline. Args:
Returns: Hits with file, line range, symbol, score, snippet, and how it matched (semantic/lexical/symbol). Use when: "where is X handled?", "find code that does Y". Requires localscope_index first. |
| localscope_impactA | Answer "where does X break if I change Y?" from the local import graph and symbol table — entirely offline. Args:
Returns: Direct dependents (files importing the target), transitive dependents, and exported symbols at risk. Use when: "what breaks if I refactor/delete this?", "who uses this function?". Requires localscope_index first. |
| localscope_statusA | Show whether a repository root has a local index, its stats (files/chunks/symbols), and the active embedder mode. Read-only, offline. Args:
Returns: Indexed state, counts, embedder mode, indexedAt timestamp. |
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 4 tools
Each tool has a clearly distinct role: building an index, searching it, analyzing impact, and checking status. There is no overlap or ambiguity among the four operations.
All tool names follow a uniform 'localscope_' prefix with a simple lower-case verb: index, search, impact, status. The naming pattern is consistent and predictable.
Four tools make for a compact, focused surface that covers the core workflows of indexing, querying, impact analysis, and health checks. It is well-scoped for a local code intelligence server without being bloated or thin.
The set covers build, search, impact analysis, and status, which is strong. A minor gap is the lack of an explicit delete/clear index operation, but re-indexing effectively replaces the index, so this is a small omission rather than a critical failure.