fix(catalog): add Context7 to optional-mcp catalog

[liuhao1024]

What does this PR do?

Adds Context7 (@upstash/context7-mcp) to the optional-mcp catalog. Context7 is a tools-only MCP server that provides resolve_library_id and query_docs tools for up-to-date library and version documentation queries. It requires no authentication (free, no API key).

This addresses the catalog gap where fresh Hermes sessions cannot use Context7 unless users manually discover the npm package and write the mcp_servers stanza by hand. After this fix, users can run hermes mcp install context7 to get the Context7 tools automatically.

The approach adds a minimal manifest.yaml file (34 lines) that follows the existing catalog schema, matching the patterns used by linear, n8n, and unreal-engine entries.

Related Issue

Fixes NousResearch#62675

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• optional-mcps/context7/manifest.yaml: New catalog entry for Context7 MCP server

How to Test

1. hermes mcp catalog should list Context7 as an available option.
2. hermes mcp install context7 should prompt for confirmation and register the server in ~/.hermes/config.yaml.
3. hermes mcp test context7 should discover at least 2 tools (resolve_library_id, query_docs).
4. Starting a new Hermes session should expose mcp_context7_resolve_library_id and mcp_context7_query_docs tools.

Observed result: With the manifest in place, the existing MCP catalog infrastructure (hermes_cli/mcp_catalog.py) correctly parses the manifest and enables hermes mcp install context7.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS 15.2

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

[github-actions]

⚠️ MCP catalog security review required

This PR changes the bundled MCP catalog or MCP catalog installer code. MCP entries can define local commands that users later install into mcp_servers, so this needs explicit maintainer review before merge.

A maintainer should verify:

• any new/changed optional-mcps/**/manifest.yaml command and args are expected,
• stdio transports do not use shell+egress/exfiltration payloads,
• git install refs are pinned and bootstrap commands are minimal,
• requested env vars/secrets match the upstream MCP's documented needs.

After review, add the mcp-catalog-reviewed label and re-run this check.