Command · Agent Bridges (MCP)

Hunter

Hunter hosts its own MCP server. Add it in raia CX under Skills → MCP → Edit → Integrations with your Hunter API key as a header.

External MCPAuth: API key header

How it works

Hunter hosts its own MCP server — there is no native Command credential form for Hunter. Command's page is a reference that shows the endpoint URL and transport. You add the server to an agent in raia CX under Skills → MCP → Edit → Integrations.

Before you start

A Hunter account and API key
Access to the agent in raia CX

What you need to make the connection

Field	Where to get it
Endpoint URL	https://mcp.hunter.io/mcp — the same endpoint Command's Hunter reference page lists, with a Copy button.
Transport	Streamable HTTP.
Authorization	Leave the Authorization input blank. Use + Add Header with Header Name X-API-Key and Header Value your approved Hunter key, per Hunter's official documentation.

Recommended practice: keep credentials private. If one is exposed, revoke or rotate it with the provider before reconnecting.

Setup steps

01
In raia CX, open Agents, select the agent, then open Skills.
In Launch Pad, open Agents and choose the agent you want to configure.
1. Highlight 1: Agents
On that agent, open Skills.
1. Highlight 1: Skills
02
Open MCP → Edit → Integrations and click Add Integration.
MCP before setup: RAIA MCP is incoming access; Integrations configures outgoing servers.
1. Highlight 1: RAIA MCP
2. Highlight 2: Integrations
3. Highlight 3: Set up MCP Skill
03
Enter a Name (letters, numbers, underscores and hyphens only — no spaces) and a Description, and set URL to https://mcp.hunter.io/mcp — the endpoint Command's Hunter page lists.
Hunter draft (fictional, unsaved): Name and Description.
1. Highlight 1: Name — letters, numbers, underscores and hyphens only; must start with a letter.
2. Highlight 2: Description — tell the agent when and why it should use these tools.
Hunter draft (fictional, unsaved): the Hunter MCP endpoint URL and Transport.
1. Highlight 1: URL — https://mcp.hunter.io/mcp
2. Highlight 2: Transport — Streamable HTTP.
Command lists the provider's hosted MCP endpoint (https://mcp.hunter.io/mcp) with transport Streamable HTTP. Copy the URL; credentials are entered in raia CX, not here.
1. Highlight 1: Transport: Streamable HTTP
2. Highlight 2: Endpoint URL: https://mcp.hunter.io/mcp
3. Highlight 3: Copy
04
Set Transport to Streamable HTTP. Leave Authorization blank; click + Add Header and enter Header Name X-API-Key with your Hunter key as the Header Value.
Hunter draft (fictional, unsaved): leave Authorization blank and add the X-API-Key custom header instead.
1. Highlight 1: Authorization — leave blank; use the custom header below.
2. Highlight 2: Header Name: X-API-Key
3. Highlight 3: Header Value: the approved key (blank in this draft).
05
Click Get Available Tools. Loading initially selects every returned tool — review the list and deselect tools the agent should not have. Hunter's current tools include lead and outreach writes, not just reads.
The Get Available Tools button and its prerequisite note: tools must be loaded before the integration can be created.
1. Highlight 1: Get Available Tools — appears once the URL is valid.
2. Highlight 2: Prerequisite note — tools must be loaded before you can create the integration.
06
Click the final Add Integration (it appears only after tools are loaded). If a call fails, confirm the header name and key in Hunter's API documentation and retry.