hermes - 💡(How to fix) Fix Docs request: iFlow Search MCP server configuration for Hermes Agent

Summary

I would like to propose adding a Hermes Agent docs example for using iFlow Search through MCP.

The MCP server has been published as:

• Package: @iflow-ai/search-mcp@next
• Binary: iflow-search-mcp
• Transport: stdio
• Config: environment variables only

It exposes three tools:

• iflow_web_search
• iflow_image_search
• iflow_web_fetch

Project information

• Product: iFlow Search
• Website: https://platform.iflow.cn
• API Documentation: https://platform.iflow.cn/docs/
• Repository: https://github.com/zhengyanglsun/iflow-search-js
• MCP package: https://github.com/zhengyanglsun/iflow-search-js/tree/main/packages/search-mcp
• npm scope: @iflow-ai
• Maintainer: maintained by the iFlow team, associated with Hangzhou Xingchen Qianxun Technology Co., Ltd. (杭州星辰千寻科技有限公司)

Hermes config

This has been tested successfully with Hermes using ~/.hermes/config.yaml:

mcp_servers:
  iflow-search:
    command: npx
    args:
      - -y
      - "@iflow-ai/search-mcp@next"
    env:
      IFLOW_API_KEY: YOUR_IFLOW_API_KEY

Verification command:

hermes mcp test iflow-search

Verified behavior

Hermes was able to:

• start the MCP server through npx -y @iflow-ai/search-mcp@next
• discover all three tools
• call web search successfully
• call image search successfully
• call web fetch successfully

No JSON-RPC parse errors, stdout pollution, server disconnects, or command failures were observed.

Important note

IFLOW_API_KEY must be configured in the server env block. It should not be committed to a repository.

Request

Would the Hermes maintainers be open to a docs PR adding this as an MCP server example?