mcp-semantic-search
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| indexA | Index the specs/ directory in the current project (app). Automatically skips if content hasn't changed since last index. |
| searchA | Semantic search over indexed specs in app. Returns relevant markdown chunks ranked by similarity. Optionally filter by file, section heading, or chunk type. |
| statusA | Show index status for the current project. |
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 3 tools
Each tool has a distinct, non-overlapping purpose: index builds the search index, search queries it, and status shows its state. No ambiguity exists among them.
All three tool names are single lowercase words (index, search, status) that clearly describe their action. The naming pattern is uniform and predictable.
Three tools are exactly right for a focused semantic search MCP server: index, search, and status cover the essential operations without excess or deficiency.
The set covers the core lifecycle (index, search, status) but lacks an explicit operation to clear or delete the index. This minor gap is acceptable for most use cases.