hermes - 💡(How to fix) Fix [Feature]: Add Hunter.io API key support for Composio MCP integration [1 participants]

Fix Action

Fix / Workaround

Manual env export: Users manually export HUNTER_API_KEY before running commands (current workaround)
In-skill configuration: Each skill handles its own auth (fragmented, inconsistent)
Composio OAuth: Rely entirely on Composio's OAuth flow (requires user to authenticate through Composio dashboard first)

Code Example

# ~/.hermes/.env
HUNTER_API_KEY=your_hunter_api_key_here

---

hermes config set HUNTER_API_KEY <key>

---

# ~/.hermes/config.yaml
mcp_servers:
  composio:
    url: "https://rube.app/mcp"
    # Hunter authentication would be handled through Composio OAuth

---

---
name: Hunter Automation
requires:
  mcp:
    - rube
---

Feature Request Summary

Add support for the Hunter.io API key in the Composio MCP integration to enable Hunter email intelligence workflows through the Rube MCP server.

Problem or Use Case

The Hunter.io automation skill exists in the skills directory (hunter-automation) but there's currently no explicit API key support for Hunter in the Hermes MCP/Composio configuration. This means users cannot easily authenticate with Hunter.io for email intelligence tasks like:

Domain email searching
Email verification
Email finding by person name
Lead management

Without dedicated Hunter API key handling, users need to manually configure environment variables or pass credentials through less discoverable methods.

Proposed Solution

Add Hunter.io API key configuration support following the existing pattern used for other API keys in the Hermes config system.

Implementation Options

Option A: Environment Variable Pattern (Recommended)

Add support for a HUNTER_API_KEY environment variable that gets automatically picked up by the Hunter automation skill:

# ~/.hermes/.env
HUNTER_API_KEY=your_hunter_api_key_here

Or via the hermes CLI:

hermes config set HUNTER_API_KEY <key>

Option B: MCP Server Configuration Pattern

If Hunter is available as a Composio toolkit through Rube MCP, add it to the MCP preset configuration in hermes_cli/mcp_config.py:

# ~/.hermes/config.yaml
mcp_servers:
  composio:
    url: "https://rube.app/mcp"
    # Hunter authentication would be handled through Composio OAuth

Current State Analysis

Based on code review:

Hunter Skill Exists: skills/hunter-automation/SKILL.md is documented and ready
Composio/Rube Integration: The skill references Rube MCP (requires: mcp: [rube])
No Explicit Key Support: Unlike other APIs (OpenAI, etc.), Hunter isn't currently listed in the config loader

Code References

Existing Hunter Skill Documentation

Location: ~/.hermes/skills/hunter-automation/SKILL.md

The skill already defines MCP requirements:

---
name: Hunter Automation
requires:
  mcp:
    - rube
---

Current API Key Patterns

Found in ~/.hermes/config.yaml:

Multiple provider API keys (nvidia, cerebras, google, groq, mistral, openrouter, cloudflare, etc.)

MCP Configuration Pattern

Found in ~/.hermes/hermes-agent/hermes_cli/mcp_config.py:

Supports HTTP and stdio transports
OAuth and header-based authentication
Preset system for common MCP servers

Acceptance Criteria

User can configure Hunter API key via .env file
User can configure Hunter API key via CLI command
Key is automatically loaded into environment when running Hunter automation tasks
Documentation is updated to show how to configure Hunter
Error message is clear when Hunter API key is missing

Similar Implementations

Reference these existing implementations for pattern consistency:

hermes_cli/auth.py for credential storage
hermes_cli/config.py for configuration loading
hermes_cli/mcp_config.py for MCP-specific auth patterns

Alternatives Considered

Manual env export: Users manually export HUNTER_API_KEY before running commands (current workaround)
In-skill configuration: Each skill handles its own auth (fragmented, inconsistent)
Composio OAuth: Rely entirely on Composio's OAuth flow (requires user to authenticate through Composio dashboard first)

Option A is preferred for consistency with other API key patterns in Hermes.

Feature Type

Configuration option
Integration improvement

Scope

Small (2-3 files, < 100 lines)

Contribution

I'd like to implement this myself and submit a PR

Related: The Hunter automation skill documentation already exists at skills/hunter-automation/SKILL.md and references the Composio Rube MCP server at https://rube.app/mcp.

Composio Toolkit Reference: https://composio.dev/toolkits/hunter

extent analysis

TL;DR

To add support for the Hunter.io API key in the Composio MCP integration, implement environment variable support for HUNTER_API_KEY following the existing pattern used for other API keys in the Hermes config system.

Guidance

Review the existing API key patterns in ~/.hermes/config.yaml to ensure consistency with the proposed Hunter API key configuration.
Update the hermes_cli/mcp_config.py file to include Hunter API key handling if using the MCP Server Configuration Pattern.
Test the implementation by configuring the Hunter API key via the .env file and CLI command, and verify that it is automatically loaded into the environment when running Hunter automation tasks.
Ensure that error messages are clear when the Hunter API key is missing, and update documentation to reflect the new configuration method.

Example

# ~/.hermes/.env
HUNTER_API_KEY=your_hunter_api_key_here

or via the hermes CLI:

hermes config set HUNTER_API_KEY <key>

Notes

The implementation should follow the pattern used for other API keys in the Hermes config system to maintain consistency. The proposed solution has a small scope, affecting only 2-3 files and less than 100 lines of code.

Recommendation

Apply the workaround by implementing environment variable support for HUNTER_API_KEY as described in the proposed solution, following the existing pattern used for other API keys in the Hermes config system. This approach is preferred for consistency and ease of use.