feat(mcp): add TypeWhisper catalog entry

[SeoFood]

What does this PR do?

Adds TypeWhisper to the Nous-approved MCP catalog so users can install its local speech-to-text tools with:

hermes mcp install typewhisper

The catalog entry launches the published @typewhisper/mcp@0.1.2 stdio server. TypeWhisper discovers its authenticated local API automatically on macOS and Windows; remote hosts can be configured through the MCP server's env block.

The default tool selection enables status, model listing, file transcription, history search, and read-only dictionary access. Dictionary writes and deletes remain available in the install checklist but are disabled by default.

Type of Change

• New feature

Changes Made

• Add optional-mcps/typewhisper/manifest.yaml.
• Pin the reviewed npm server version for reproducible installs.
• Document local discovery, remote token configuration, host-side file paths, and tool reconfiguration.

The branch is rebased onto current main, including #68217. Hermes no longer supports pip/PyPI wheel or sdist distribution; catalog data now comes directly from the checkout for source/Docker installs and from the bundled optional-mcps store path for Nix installs.

How to Test

scripts/run_tests.sh tests/hermes_cli/test_mcp_catalog.py tests/hermes_cli/test_dashboard_admin_endpoints.py

The targeted suite passes all 129 tests on the current PR head.

The real install path was also exercised against a running TypeWhisper instance with an isolated HERMES_HOME:

HERMES_HOME="$(mktemp -d)" .venv/bin/hermes mcp install typewhisper

Hermes discovered all 10 tools and persisted the six manifest defaults.

Checklist

• Read the contributing guide
• Conventional commit used
• Searched existing issues and PRs for TypeWhisper
• Focused change with no unrelated refactors
• Current catalog and dashboard contract tests cover the new manifest
• Tested on macOS 27.0
• Cross-platform behavior considered: the MCP package supports macOS and Windows discovery, plus explicit remote URL/token configuration
• Documentation/config examples updated in the manifest; no core config keys or architecture changed

[tonydwb]

Code Review Summary

Verdict: Comment

30 PRs reviewed (batch: 64044-63999). See aggregate summary at PR 64044.

---

Reviewed by Hermes Agent

[teknium1]

Thanks for the focused catalog contribution. The manifest uses the existing MCP-catalog route and its exact @typewhisper/mcp@0.1.2 pin matches the current catalog contract.

Problems

• Blocking: the new manifest is not declared in wheel data files. pyproject.toml:323-336 requires one [tool.setuptools.data-files] target per optional-mcps/<name>/manifest.yaml, but it currently lists only linear and n8n. Because hermes_cli/mcp_catalog.py:136-140 resolves the catalog from the installed distribution, packaged installs would not contain this entry even though it works from a source checkout.

Suggested changes

• Add "optional-mcps/typewhisper" = ["optional-mcps/typewhisper/manifest.yaml"] to pyproject.toml and add a regression guard for manifest/data-files parity.

Automated hermes-sweeper review.