Skip to content
The Register

MCP Enricher — Look Up Every Row in Your Own Apps

Enrich every row of a dataset by calling a tool on an app you connected as an Apify MCP connector — a CRM, a project tracker, an internal database — and merge the reply back into the row. Your credentials never touch the Actor. Dry run by default.

MCP Enricher — Look Up Every Row in Your Own Apps returns 5 documented output fields, including tool, reason, unmapped, args and status. Every field carries a declared type, a written description and an example value. 1 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription
5
Output fields
9
Inputs
1
Run
2026-10-16
Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

FieldTypeWhat it holdsExample
toolstring | number | boolean | array | objectnullTool as recorded for this row.[]
reasonstringnullWhy this row carries its status.matched
unmappedarraynullUnmapped as recorded for this row.[]
argsstring | number | boolean | array | objectnullArgs as recorded for this row.[]
statusstring | number | boolean | array | objectnullOutcome recorded for this row.ok

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "tool": "[]",
  "reason": "matched",
  "unmapped": [],
  "args": "[]",
  "status": "ok"
}

03 — input

What you give it

InputTypeDescription
connectorstringoptionalThe app to query. Authorise it once in Settings → API & Integrations, then pick it here. The Actor never sees your credentials — the platform injects them server-side.
datasetIdstringoptionalThe dataset id from a previous run (its defaultDatasetId). Leave empty to use 'items' below instead.
itemsarrayoptionalRows supplied directly, one object per row. Used only when 'datasetId' is empty.
toolNamestringoptionalLeave empty and the Actor picks the tool that looks like a lookup (get, search, find, list, read…), and tells you which it chose. Name one to be exact — a name that does not exist is refused rather than substituted.
fieldMapstringoptionalJSON mapping from the tool's argument names to your row's field names, e.g. {"query":"company_name"}. Leave empty and row fields whose names the tool already declares are passed through unchanged.
outputFieldstringoptionalThe field the tool's reply is written into. The companion fields <name>_ok, <name>_error and <name>_tool are written beside it, so a failed lookup is visible rather than blank.
maxItemsintegeroptionalHard limit on tool calls. The first N rows are enriched, in the order the dataset gives them.
skipOnErrorbooleanoptionalON by default: a row the tool could not answer is kept with its error recorded, and the run continues. Turn it off to stop at the first failure.
dryRunbooleanoptionalON by default. Reports the tools the connector offers, which one would be called, and the exact arguments for the first row, without calling it.

04 — run

Run MCP Enricher on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

05 — questions

Asked before running it

5 of 5 fields described

What does MCP Enricher — Look Up Every Row in Your Own Apps return?
It returns 5 documented output fields: tool, reason, unmapped, args and status. Each field declares its type, a description of what it holds, and an example value.
What input does MCP Enricher — Look Up Every Row in Your Own Apps take?
All 9 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
Does MCP Enricher — Look Up Every Row in Your Own Apps need an API key or login?
No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
How do I run MCP Enricher — Look Up Every Row in Your Own Apps?
It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.