Your agent can read every Instantly reply.
Now it can tell which ones want to buy.

Published 30 September 2026 · Instantly’s MCP documentation checked the same day

What you need

• An Instantly API v2 key, created under Settings, Integrations, API Keys, with the scopes your workflow needs (see Instantly’s MCP quickstart).
• A SignalPipe operator key, from your console once you are on a plan.
• Claude Code, or any MCP client that can hold two servers.

1. Connect both servers

claude mcp add --transport http instantly https://mcp.instantly.ai/mcp \
  --header "Authorization: Bearer YOUR_INSTANTLY_API_KEY"

claude mcp add --transport http signalpipe https://api.signalpipe.io/mcp \
  --header "Authorization: Bearer YOUR_SIGNALPIPE_OPERATOR_KEY"

Instantly also accepts its key without the Bearer prefix, or in an x-instantly-api-key header (see its authentication page). To share the setup with a team, use the project’s .mcp.json. Claude Code fills in environment variables there, so neither key is committed:

{
  "mcpServers": {
    "instantly": {
      "type": "http",
      "url": "https://mcp.instantly.ai/mcp",
      "headers": { "Authorization": "Bearer ${INSTANTLY_API_KEY}" }
    },
    "signalpipe": {
      "type": "http",
      "url": "https://api.signalpipe.io/mcp",
      "headers": { "Authorization": "Bearer ${SIGNALPIPE_OPERATOR_KEY}" }
    }
  }
}

Run /mcp inside Claude Code to check both are connected.

2. Tell SignalPipe what you sell

The judges decide who is a buyer of your product, so describe it once: who buys it, what it does for them, and a few sentences in the buyer’s voice. Claude Code can interview you and do it with suggest_anchors and add_product; the Claude Code recipe has the prompt.

3. Judge the replies

Use Instantly to list the replies to my campaigns from the last 7 days.
For each reply, call SignalPipe's score_signal with the reply as text,
my product, source_hint "email", and the email we sent them as context.
Then sort them: buyers first, then the ones where the judges split,
then everything else. Don't reply to anyone yet.

The context matters. A reply like “sure, send more info” means little on its own; with the email it answers, the judges read it properly while still judging the reply’s own author. Each verdict says whether the reply reads as a buyer, a competitor mention, borderline or noise, whether the three judges were needed, and whether they agreed. When they split, read that reply yourself. A verdict marked degraded means the panel could not run, so treat it as provisional.

4. Draft, approve, send

For the top three, draft a reply that answers what each person asked,
in two or three sentences. Show me every draft. Send only the ones I
approve, from Instantly, in the same thread.

The drafting and the sending happen in your agent and your Instantly workspace. SignalPipe’s part ends at the verdict, so the replies go out from your own accounts, when you say so.

5. Keep the warm ones warm (optional)

Track the people I replied to as prospects in SignalPipe with
track_prospect, and when they write back, record it with record_reply so
I can see who is warming up and who asked not to be contacted.

record_reply reads each new message and updates the prospect’s temperature, stage and objections. It also flags when someone asks not to be contacted, so your agent stops.

What it costs

SignalPipe meters judging in judgements. One judgement is one run of the three-judge panel, and a reply that is clearly a buyer or clearly not is decided without the panel and costs nothing. Plans start at $29 a month for 3,000; see pricing.