MCP Output Router — Send Any Dataset to Your Own Apps

Point this at a dataset and at an app you have connected as an Apify MCP connector, and every row is written into that app — a Notion database, a Slack channel, a Supabase table, a CRM, anything speaking MCP.

Your credentials never touch this Actor. You authorise the connector once in Apify Console; the platform injects the credentials through a proxy. The Actor only ever holds its own run token.

Why this exists

The sibling Actors that write to a specific app each need you to paste an API key or a service-account JSON — and then to keep it working. A connector is authorised once and then chosen from a dropdown, and the credentials stay on Apify's side.

Two modes

Dry run — the default, and free. Nothing is written. You get back the tools the connector offers, which one would be called, and the exact arguments for your first row:

Field	Meaning
tools_offered	every tool the connector exposes
tool / tool_reason	the one that would be called, and why
sample_arguments	exactly what the first row would send
coerced_keys	arguments whose type was fixed (e.g. "1,250" → 1250)
dropped_keys	arguments the tool does not accept
missing_required	required arguments your row could not supply

Real run — turn dryRun off. One tool call per row, up to maxItems.

Every row reports whether it was accepted

Field	Meaning
index	which source row
tool	the tool called
status	written or failed
ok	boolean, so you can filter
error	why it failed — a missing required argument, or the message the destination returned
detail	the destination's own reply, truncated
argument_keys / args_preview	what was sent, so a wrong mapping is visible

A run also writes a SUMMARY record: completed, partial (some rows failed) or failed — with the counts and one next action.

Nothing is invented

• A name that does not exist is refused, not substituted. Ask for create_page and the connector has no such tool, and the run stops and tells you. Quietly writing to a different tool is the failure mode this Actor must never have.
• With no tool named, the Actor picks the only tool that looks like a write action (create, add, append, send, write, post, update…) and says which and why. Several candidates and none looking like a write action → it asks you to name one.
• A number that will not parse is left alone, not zeroed. Sending 0 where a buyer meant "twelve" would corrupt a real record.
• Success means the destination accepted the call. It does not prove the record is visible in your app; the SUMMARY says so.

Cost

The default dataset item event charges for each result row. A dry run writes one plan row, so it incurs one result-row charge plus the Actor start event, even though it sends nothing to the connected app. A real run writes one result row per attempted item, including failed attempts.

Adjusting it

Everything that decides which tool is called and what is passed lives in src/lib/mcp-router.js — tool selection, the field map, type coercion, required-argument checks. It is pure: no SDK, no network. It is covered by tests that run without a connector or an Apify account.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• MCP Output Router — Send Any Dataset to Your Own Apps declares all 5 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of MCP Output Router include tool, reason, unmapped, args and status.
• MCP Output Router needs no API key, login or account of any kind before its first run.
• Every one of MCP Output Router's 7 inputs is optional, so it runs with no configuration at all.
• Every number published about MCP Output Router is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• MCP Output Router is filed under integrations, developer tools and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• MCP Output Router reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

FAQ

What does MCP Output Router return?

It returns 5 documented output fields — tool, reason, unmapped, args and status — each with a declared type and a written description. The full schema is below.

What does MCP Output Router require to run?

Nothing. All 7 inputs are optional and ship with working defaults.

Does MCP Output Router need an API key?

No. It reads only public data and asks for no account.

How is MCP Output Router billed?

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.