en es ja ko zh

Hermes Search MCP Server

Name: Hermes Search MCP Server
Author: Cognitive-Stack

by Cognitive-Stack

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Hermes 搜索 MCP 服务器 🔍

🔌与 Cline、Cursor、Claude Desktop 和任何其他 MCP 客户端兼容！

模型上下文协议 (MCP) 是一种开放标准，使 AI 系统能够与各种数据源和工具无缝交互，促进安全的双向连接。

Hermes Search MCP 服务器提供：

对结构化/非结构化数据的全文和语义搜索功能
Azure 认知搜索中的文档索引和管理
具有可自定义参数的高效搜索操作
使用 TypeScript 进行类型安全操作

先决条件🔧

在开始之前，请确保您已：

Azure 认知搜索服务和凭据
Claude 桌面或光标
Node.js（v20 或更高版本）
已安装 Git（仅在使用 Git 安装方法时才需要）

Related MCP server: Azure AI Search MCP Server

Hermes Search MCP 服务器安装⚡

使用 NPX 运行

npx -y hermes-search-mcp@latest

通过 Smithery 安装

要通过 Smithery 自动为 Claude Desktop 安装 Hermes Search MCP Server：

npx -y @smithery/cli install @hermes-search/mcp --client claude

配置 MCP 客户端 ⚙️

配置 Cline 🤖

在 Cline 中设置 Hermes Search MCP 服务器的最简单方法是通过市场单击一下：

在 VS Code 中打开 Cline
点击侧边栏中的 Cline 图标
导航到“MCP 服务器”选项卡（4 个方块）
搜索“Hermes Search”，点击“安装”
出现提示时，输入 Azure 认知搜索凭据

或者，您可以在 Cline 中手动设置 Hermes Search MCP 服务器：

打开 Cline MCP 设置文件：

# For macOS:
code ~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

# For Windows:
code %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

将 Hermes Search 服务器配置添加到文件中：

{
  "mcpServers": {
    "hermes-search-mcp": {
      "command": "npx",
      "args": ["-y", "hermes-search-mcp@latest"],
      "env": {
        "AZURE_SEARCH_ENDPOINT": "your-search-endpoint",
        "AZURE_SEARCH_API_KEY": "your-api-key",
        "AZURE_SEARCH_INDEX_NAME": "your-index-name"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

如果 Cline 已运行，请保存文件并重新启动它。

配置光标🖥️

注意：需要 Cursor 版本 0.45.6 或更高版本

要在 Cursor 中设置 Hermes Search MCP 服务器：

打开游标设置
导航至“功能”>“MCP 服务器”
点击“+ 添加新的 MCP 服务器”按钮
填写以下信息：
- 名称：输入服务器的昵称（例如，“hermes-search-mcp”）
- 类型：选择“命令”作为类型
- 命令：输入运行服务器的命令：GXP5
重要提示：将环境变量替换为 Azure 认知搜索凭据

配置 Claude 桌面应用程序🖥️

对于 macOS：

# Create the config file if it doesn't exist
touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

# Opens the config file in TextEdit
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

对于 Windows：

code %APPDATA%\Claude\claude_desktop_config.json

添加 Hermes Search 服务器配置：

{
  "mcpServers": {
    "hermes-search-mcp": {
      "command": "npx",
      "args": ["-y", "hermes-search-mcp@latest"],
      "env": {
        "AZURE_SEARCH_ENDPOINT": "your-search-endpoint",
        "AZURE_SEARCH_API_KEY": "your-api-key",
        "AZURE_SEARCH_INDEX_NAME": "your-index-name"
      }
    }
  }
}

在 Claude 桌面应用程序中的使用

安装完成并配置好 Claude 桌面应用程序后，您必须完全关闭并重新打开 Claude 桌面应用程序才能看到 hermes-search-mcp 服务器。您应该会在应用程序左下角看到一个搜索图标，指示可用的 MCP 工具。

Hermes 搜索示例

搜索文件：

Search for documents containing "machine learning" in the Azure Cognitive Search index, returning the top 10 results.

索引内容：

Index the following documents into Azure Cognitive Search: [{"id": "1", "title": "AI Overview", "content": "Artificial Intelligence is..."}]

删除索引：

Delete the current Azure Cognitive Search index.

故障排除🛠️

常见问题

未找到服务器
- 通过运行npm --version来验证 npm 安装
- 检查 Claude Desktop 配置语法
- 通过运行node --version确保正确安装了 Node.js
Azure 搜索凭据问题
- 确认 Azure 认知搜索凭据有效
- 检查配置中的凭据是否正确设置
- 验证凭证周围没有空格或引号
索引访问问题
- 验证 Azure 认知搜索服务中是否存在索引
- 检查索引权限
- 确保 API 密钥具有适当的访问权限

致谢✨

MCP 规范的模型上下文协议
克劳德桌面版的 Anthropic
Microsoft Azure 认知搜索

Available Tools

3 tools

delete-indexA

Delete the Azure Cognitive Search index

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, and the description lacks details about behavioral traits such as permanence, required permissions, or side effects. As a destructive operation, more transparency is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence with no extraneous words. It is concise and front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with no parameters or output schema, the description is minimally complete. However, it lacks context about effects or prerequisites, which would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With no parameters, the baseline is 4. The description adds minimal but adequate meaning by specifying the operation type and target, which suffices given the absence of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Delete' and the resource 'Azure Cognitive Search index', making the action unambiguous. It effectively distinguishes from sibling tools like index-content and search-documents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., when deletion is appropriate or prerequisites). The description only states the action without context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

index-contentB

Index or update documents in Azure Cognitive Search

ParametersJSON Schema

Name	Required	Description	Default
`documents`	Yes	Array of documents to index

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states 'Index or update' without explaining side effects, permissions, or whether documents are overwritten or merged. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with purpose, and is not verbose. However, it sacrifices necessary details for brevity, missing usage and behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple schema (1 param, no output schema) and lack of annotations, the description is too minimal. It fails to explain document handling (e.g., partial updates, conflict resolution) or the indexing process.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, providing a baseline of 3. The description repeats the schema's 'Array of documents to index' without adding extra meaning, such as required fields or document structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Index or update') and the resource ('documents in Azure Cognitive Search'), with a specific verb and resource. It distinguishes from sibling tools 'delete-index' and 'search-documents' by focusing on adding/updating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus its siblings. There is no mention of prerequisites or alternative tools for deletion or searching, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search-documentsB

Search documents in Azure Cognitive Search index

ParametersJSON Schema

Name	Required	Description
`top`	No	Number of results to return (default: 5)
`query`	Yes	The search query to execute
`filter`	No	OData filter expression
`select`	No	Fields to include in the results

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description does not disclose behavioral traits like pagination, relevance scoring, access requirements, or result format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it is somewhat underspecified for a search tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is too minimal. It does not explain search behavior, result structure, or how parameters interact, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Search) and resource (documents in Azure Cognitive Search index), and distinguishes from sibling tools (delete-index, index-content) which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. No mention of prerequisites, limitations, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv1.0.0Apr 19, 2025
- First observeddelete-index
- First observedindex-content
- First observedsearch-documents

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-06-04 09:40 across 3 tools

Disambiguation5/5

Each tool targets a distinct operation: deleting an index, indexing content, and searching documents. No overlap in purpose.

Naming Consistency5/5

All tools follow a consistent verb-noun pattern with hyphens (delete-index, index-content, search-documents), making them predictable.

Tool Count4/5

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.

Completeness3/5

Missing critical operations like creating an index or listing indexes. The server assumes an existing index, limiting its standalone usability.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

Needle
com.needle-ai.mcp
The Needle MCP server enables semantic search on documents stored in files like PDFs, DOCX, and XLSX by connecting AI applications to external data sources. It provides capabilities to create and manage document collections, perform natural language searches on stored content, and retrieve relevant information without requiring exact keyword matches.
RAG Systems Search File Systems
2
ragie
com.mcparmory
Ingest, manage, and retrieve documents for RAG-powered AI applications
RAG Systems Databases Knowledge & Memory
2
Ragora A
io.github.mregmi
Search your knowledge bases from any AI assistant using hybrid RAG.
RAG Systems Search Knowledge & Memory
2
Ninelayer
in.ninelayer
Agent-native search engine with live web research optimized for AI agents.
Search Agent Orchestration
2

Related MCP Servers

AXYS MCP Lite
Search RAG Systems Databases
rajesh-siliconvalleycloudit
A
license
Not graded
quality
D
maintenance
Enables AI assistants to search through structured databases and unstructured content (documents, videos, files) using natural language queries with semantic understanding.
Updated 10 months ago (2025-12-01 13:03 UTC)
MIT
Azure AI Search MCP Server
RAG Systems Search Vector Databases
mm-repos
A
license
Not graded
quality
D
maintenance
Enables Claude to search and retrieve documents from Azure AI Search indexes with intelligent summarization and analysis using LangGraph workflows and optional Google Gemini integration.
Updated a year ago (2025-09-05 20:58 UTC)
MIT
NRTSearch MCP Server
Search RAG Systems Databases
tvergilio
A
license
Not graded
quality
D
maintenance
Enables AI assistants to search and query Lucene/NRTSearch indexes using natural language, supporting full Lucene query syntax including Boolean, phrase, range, wildcard, and fuzzy searches with highlighting and custom field retrieval.
Updated a year ago (2025-07-05 07:31 UTC)
MIT
Azure AI Search MCP Server
Cloud Platforms Search AI & Machine Learning
henryperkins
F
license
Not graded
quality
D
maintenance
Enables AI assistants to manage Azure AI Search services, including indexes, documents, indexers, and skillsets, via the Model Context Protocol.
Updated a year ago (2025-08-23 05:59 UTC)
-

Hermes 搜索 MCP 服务器 🔍

先决条件🔧

Hermes Search MCP 服务器安装⚡

使用 NPX 运行

通过 Smithery 安装

配置 MCP 客户端 ⚙️

配置 Cline 🤖

配置光标🖥️

配置 Claude 桌面应用程序🖥️

对于 macOS：

对于 Windows：

添加 Hermes Search 服务器配置：

在 Claude 桌面应用程序中的使用

Hermes 搜索示例

故障排除🛠️

常见问题

致谢✨

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches