vhdl-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VHDL_RAG_MCP_CONFIG | No | Path to the vhdl-rag-mcp configuration file. Optional; the default location is ~/.config/vhdl-rag/config.toml, and a commented template is created on first run. Can also be set with the --config PATH command-line flag. | ~/.config/vhdl-rag/config.toml |
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_vhdlA | Search VHDL source: entities, architectures, processes, packages,
functions — semantic + exact-identifier hybrid search.
|
| search_docsB | Search VHDL-related documentation: coding standards, design
guides, conventions (one result per section). |
| search_codeA | Search general source code (C/C++, Python, ...): one result per
function/class. |
| search_knowledgeA | Search ALL domains (VHDL, documentation, code) at once, fused with RRF so the domains interleave fairly. Use when the question may span domains (e.g. a design requirement in the docs implemented in VHDL and tested in C). |
| get_sourceA | Read the exact current content of an indexed file (or a line
range) from the synced repository, with commit attribution.
|
| repository_statusA | Show every configured repository: category, ref, enabled domains, last indexed commit, last sync time, and any sync error. |
| sync_repositoriesA | Incrementally sync repositories (default: all): fetch the ref, chunk changed files, update the index. Safe to call any time; failures are contained per repository and reported. |
| reindex_repositoryB | Fully reindex one repository (drops and rebuilds all of its chunks). Use after config changes or to repair a drifted index. |
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 8 tools
Each tool has a clearly distinct role: domain-scoped searches (docs, VHDL, code) are separated from a fused all-domain search, and source retrieval plus sync/reindex operations are unambiguous. The descriptions reinforce the boundaries, so an agent should rarely misselect.
Most tools follow a clear verb_noun pattern: search_docs, search_vhdl, search_code, search_knowledge, get_source, sync_repositories, and reindex_repository. repository_status breaks the pattern by using a noun phrase, but the overall naming is still predictable and readable.
Eight tools is well-scoped for a RAG/search MCP server: domain-specific searches, a combined search, source retrieval, status, and index maintenance each earn their place. There is no obvious bloat or redundancy.
The server covers the full expected surface for VHDL RAG: searching documentation, VHDL source, general code, and all domains together, plus retrieving exact source content and managing repository indexing state. The sync and reindex tools close the otherwise common operational gap.