Forager MCP server

@pipeworx/forager

Find a person's phone number from their LinkedIn profile URL, via Forager (forager.ai). Part of enrich-waterfall's new enrichfindphone finder rotation (fleet #2860).

Part of Pipeworx — an MCP gateway connecting AI agents to 1743+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

phone number + type. Requires BOTH a Forager account id and an API key.

• foragerfindphone(linkedinurl?, personid?, accountId, apiKey) —

Auth

BYO only. Pass your Forager account id as accountId and your API key as apiKey (header X-API-KEY, with the account id as a PATH segment: /api/{account_id}/...). Both are on your Forager dashboard. No platform key (D4).

Data sources

• https://api-v2.forager.ai/api/{accountid}/datastorage/personcontactslookup/phonenumbers/

Verification notes (fleet #2860, 2026-10-08, no vendor key held) — THIS PACK HAS THE WEAKEST CONFIRMATION IN THE BATCH

.../phone_numbers/ with account id "0" returns HTTP 403 (never 404), so the path and the account-id-in-path convention are real.

• The URL path is confirmed live. Every auth shape tried against

X-API-KEY: invalidkey123, Authorization: Api-Key invalidkey123, and Authorization: Bearer invalidkey123 all return the byte-identical {"detail":"Authentication credentials were not provided."}. A placeholder-key probe cannot tell "wrong header" apart from "right header, garbage key" when the server's generic-scheme message is this generic. X-API-KEY is used here because that is what search results describing Forager's own docs name, but this is the one auth shape in this batch that should be treated as a hypothesis, not a confirmed fact, until a real key either works or returns a DIFFERENT 401/403 body.

• The header name is NOT independently confirmed. No header,

confirmed schema. We could not read docs.forager.ai's own schema page for this specific endpoint (only sibling endpoints — detail lookup, reverse-by-email, reverse-by-phone, role search — turned up in what we could fetch). This pack sends {"linkedinurl": ...} or {"personid": ...} and reads a phonenumbers array (string or {number, type} objects) back, by analogy with Forager's REST conventions elsewhere. If a real key gets a 200 with a different shape, findPhone() in src/index.ts is the only place that needs fixing.

• **The request/response body fields are a best-effort guess, not a

pack: the auth header name, the request body field name, the response field name, and whether accountId is even the right concept (vs. the account id being derivable from the key itself).

• **Not verified (no key held), and more load-bearing than usual for this

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "forager": {
      "url": "https://gateway.pipeworx.io/forager/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/forager/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.