Web intelligence, verified B2B contacts, and a persistent knowledge graph for AI agents.
If you already use Forage — Web Intelligence & Knowledge Graph, the forage — web intelligence & knowledge graph mcp server is the piece that lets your assistant work with it directly. Web intelligence, verified B2B contacts, and a persistent knowledge graph for AI agents.
You ask it: "Who are Stripe's main competitors?" It tells you confidently about companies that don't exist. You ask: "Find me 50 qualified leads." It returns hallucinations with made-up email addresses. You say: "What did you learn about this market last month?" It says: "I have no memory of last month."
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
search_web — Search the web, get real resultsscrape_page — Extract clean text from any URLget_company_info — Domain to full company profile with contactsfind_emails — Discover verified B2B emails with confidence scoresfind_local_leads — Find local businesses by type and locationfind_leads — Generate B2B lead lists filtered by title/location/industrylist_verified_actors — Browse available data source actorsget_actor_schema — Get input schema for any actorcall_actor — Run any data actor with custom inputsearch_apify_store — Search 1500+ data actorsquery_knowledge — Search the graph for previously discovered entitiesenrich_entity — Full profile with all relationships from the graphSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: APIFY_API_TOKEN, YOUR_APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Forage — Web Intelligence & Knowledge Graph's toolset — search_web, scrape_page, get_company_info and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ErnestaLabs; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_web | Search the web, get real results |
| scrape_page | Extract clean text from any URL |
| get_company_info | Domain to full company profile with contacts |
| find_emails | Discover verified B2B emails with confidence scores |
| find_local_leads | Find local businesses by type and location |
| find_leads | Generate B2B lead lists filtered by title/location/industry |
| list_verified_actors | Browse available data source actors |
| get_actor_schema | Get input schema for any actor |
| call_actor | Run any data actor with custom input |
| search_apify_store | Search 1500+ data actors |
| query_knowledge | Search the graph for previously discovered entities |
| enrich_entity | Full profile with all relationships from the graph |
| find_connections | Find relationship paths between any two entities |
| add_claim | Store a sourced assertion with confidence score |
{
"mcpServers": {
"forage": {
"command": "npx",
"args": ["-y", "@anthropic/mcp-proxy", "https://ernesta-labs--forage.apify.actor/mcp"],
"env": { "APIFY_API_TOKEN": "YOUR_APIFY_TOKEN" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| APIFY_API_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_APIFY_TOKEN | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.