Semantic Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_STUDIO | No | API key for Gemini-based searchers (AI Studio) | |
| REPO_PATH | No | Path to the repository to search (defaults to current directory) | . |
| SEARCHER_TYPE | No | Searcher implementation to use (default: sgr_gemini_flash_lite) | sgr_gemini_flash_lite |
| CLAUDE_API_KEY | No | API key for Claude-based searchers | |
| GEMINI_API_KEY | No | API key for Gemini-based searchers | |
| GOOGLE_API_KEY | No | API key for Gemini-based searchers | |
| OPENAI_API_KEY | No | API key for OpenAI-based searchers | |
| ANTHROPIC_API_KEY | No | API key for Claude-based searchers | |
| VERTEX_AI_API_KEY | No | API key for Gemini-based searchers (Vertex AI) |
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 |
|---|---|
| semantic_searchD | MCP wrapper around core function. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'semantic_search' has a clear and distinct purpose that cannot be confused with any other tool in the set.
The tool name 'semantic_search' follows a consistent snake_case pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and matches the server's purpose.
A single tool is generally too few for most server purposes, as it limits functionality and can lead to dead ends in agent workflows. For a semantic search server, one tool feels thin and under-scoped, lacking operations like filtering, indexing, or result management.
The tool set is severely incomplete for a semantic search domain. It only provides a basic search function, with obvious gaps such as indexing documents, managing search indices, updating or deleting entries, or handling advanced search parameters, which are essential for comprehensive semantic search operations.