ProspectingConnector
Forager
Search job postings and company firmographics, or enrich a person's email and phone, from Claude or ChatGPT, through Tulina's own MCP server.
Official site: forager.ai
What it can do
3 read/1 send
- 01Read
Search job postings by company, title, location or remote status
- 02Read
Search organizations by industry, headcount or the technologies they run
- 03Send
Enrich a person — work emails, personal emails, phone numbers
- 04Read
Read a domain's technology stack, and check the credit balance
Two things shape how a workflow should call this. Every search and every lookup spends a credit, so asking for the count first and the page second is the difference between a cheap question and an expensive one. And the filters take numeric ids, never free text: locations: ["Paris"] matches nothing at all until Paris has been resolved to its id, and it fails by returning an empty result rather than an error.
How do you connect Forager to Claude and ChatGPT?
Through Tulina's own MCP server. Search job postings or organizations, enrich a person's work and personal email or phone, or check a domain's technology stack, in the same chat as the prospecting workflow it feeds, whether that chat is Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Forager once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Forager at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Forager returns something usable instead of something generic.
Processes that run on Forager
None published yet.