silica-core
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SILICA_VAULT | No | The root folder served by the MCP server. If not set, the server serves the folder the client was opened in. | |
| SILICA_STT_BASE_URL | No | Base URL for a speech-to-text endpoint, used to index audio and video files. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| silica_filesA | Ask what the index could see before trusting a search or calling
absence. Inventory of the root and what the index did with each file: |
| silica_searchA | For a question that names no identifier (what a behaviour is, where
it is decided, why), call this before any grep (a Grep tool, or
grep or rg in a shell), Glob or Read: it ranks
passages and, in a source tree, the functions, methods, classes and
constants themselves, by the question's words and their vectors.
Do not grep for the words of a question; grep
for an exact string or a symbol name you already know. Each hit carries
its densest |
| silica_readA | Read a located slice before citing it: lines |
| silica_code_packA | Use before editing or explaining a source file, or when a traceback or
a diff names |
| silica_write_noteA | Write one note atomically, as given, then lint it: |
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 5 tools
Each tool targets a distinct action: inventory (silica_files), semantic search (silica_search), slice reading (silica_read), symbol packing (silica_code_pack), and note writing (silica_write_note). However, silica_code_pack and silica_read both return code context and could be confused for symbol retrieval, though descriptions clarify packed vs. located slices.
All tools use the consistent `silica_` prefix followed by a snake_case noun or verb_noun (silica_code_pack, silica_files, silica_search, silica_read, silica_write_note). The pattern is predictable and readable throughout.
Five tools are well-scoped for a code and document indexing core: inventory, search, read, pack, and note writing. Each covers a distinct slice of the lifecycle without redundancy.
The surface covers discovery (search, files), reading (read, code_pack), and note creation, but lacks explicit update/delete operations for notes and any index management (e.g., rebuild or reindex). These gaps are minor and can be worked around with external tools like git.