Hermes Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_SEARCH_API_KEY | Yes | Your Azure Cognitive Search API key | |
| AZURE_SEARCH_ENDPOINT | Yes | Your Azure Cognitive Search service endpoint URL | |
| AZURE_SEARCH_INDEX_NAME | Yes | The name of your Azure Cognitive Search index |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-documentsB | Search documents in Azure Cognitive Search index |
| index-contentB | Index or update documents in Azure Cognitive Search |
| delete-indexA | Delete the Azure Cognitive Search 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 3 tools
Each tool targets a distinct operation: deleting an index, indexing content, and searching documents. No overlap in purpose.
All tools follow a consistent verb-noun pattern with hyphens (delete-index, index-content, search-documents), making them predictable.
Three tools is on the low side but covers the core search lifecycle (index, search, delete). Slightly under but reasonable for a focused MCP server.
Missing critical operations like creating an index or listing indexes. The server assumes an existing index, limiting its standalone usability.