docs(mcp): add iFlow Search server example

[wesleysimplicio]

What does this PR do?

Adds a copy-ready iFlow Search MCP server example to the Hermes MCP guide.

Root cause

Issue #29250 asked for a concrete Hermes configuration example for iFlow Search. Without a documented snippet, users have to infer the command shape, environment variable placement, and tool names from the upstream package themselves.

Fix

• Adds an iFlow Search entry to the practical MCP examples.
• Uses the published @iflow-ai/search-mcp@next stdio server through npx -y.
• Keeps the API key in the server env block instead of in the command string.
• Disables unused resource and prompt wrappers for a narrower tool surface.
• Documents the expected Hermes tool names and a simple verification command.

Why this shape

This is docs-only because the MCP server is already published and does not require Hermes runtime changes. The example stays narrow: one server, one env var, and the registered search tool names users need to verify setup.

Tests

• npm view @iflow-ai/search-mcp@next name version bin repository dist-tags --json
• git diff --check -- website/docs/guides/use-mcp-with-hermes.md
• npm --prefix website run build -- --locale en

Closes #29250

Related PRs / issues

• Related to Docs request: iFlow Search MCP server configuration for Hermes Agent #29250.

Original body

## What does this PR do?

Adds a copy-ready iFlow Search MCP server example to the Hermes MCP guide.

Problem

Issue #29250 asked for a concrete Hermes configuration example for iFlow Search. Without a documented snippet, users have to infer the command shape, environment variable placement, and tool names from the upstream package themselves.

What this changes

• Adds an iFlow Search entry to the practical MCP examples.
• Uses the published @iflow-ai/search-mcp@next stdio server through npx -y.
• Keeps the API key in the server env block instead of in the command string.
• Disables unused resource and prompt wrappers for a narrower tool surface.
• Documents the expected Hermes tool names and a simple verification command.

Why this shape

This is docs-only because the MCP server is already published and does not require Hermes runtime changes. The example stays narrow: one server, one env var, and the registered search tool names users need to verify setup.

Tests

• npm view @iflow-ai/search-mcp@next name version bin repository dist-tags --json
• git diff --check -- website/docs/guides/use-mcp-with-hermes.md
• npm --prefix website run build -- --locale en

Closes #29250

---

Generated by Hermes Turbo

[zhengyanglsun]

Status update — two changes since this PR was opened:

1. @iflow-ai/search-mcp@0.1.0 is now live on npm latest (verifiable with npm view @iflow-ai/search-mcp dist-tags).
2. The Official MCP Registry entry io.github.zhengyanglsun/iflow-search has been republished at version 0.1.0; the prior 0.1.0-pre.2 entry is retained but no longer latest.

The stdio wire surface is unchanged from the prerelease used for validation:

• tool names: iflow_web_search, iflow_image_search, iflow_web_fetch
• server transport: stdio
• package: @iflow-ai/search-mcp

The current PR uses @iflow-ai/search-mcp@next, which remains correct for following prereleases. Bare npx -y @iflow-ai/search-mcp now resolves to stable 0.1.0.

Happy to refresh the branch to use the stable install form if maintainers prefer. This is a community / third-party integration; no implied Hermes endorsement.

[wesleysimplicio]

Closing non-fix PR as requested — mantendo apenas PRs de fix.