Reducto MCP integration for AI agents.
Connect AI agents to Reducto through 3 structured actions, including extract data, parse document, and split document. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Reducto integration exposes
The Reducto Agent App exposes 3 provider-backed actions for ai, productivity, and data work. Its current contract lets an authorized agent extract structured json from a reducto-supported document url or file id using a caller-supplied json schema, parse a reducto-supported document url or file id into structured chunks, blocks, and document metadata, and split a reducto-supported document url or file id into named page sections using natural-language section descriptions. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Reducto account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Reducto capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
extract_dataREVIEWExtract structured JSON from a Reducto-supported document URL or file id using a caller-supplied JSON Schema.
INPUTS: documentUrl / schema / systemPrompt / parsing / settings
parse_documentREVIEWParse a Reducto-supported document URL or file id into structured chunks, blocks, and document metadata.
INPUTS: documentUrl / enhance / retrieval / formatting / spreadsheet
split_documentREVIEWSplit a Reducto-supported document URL or file id into named page sections using natural-language section descriptions.
INPUTS: documentUrl / splitDescription / splitRules / parsing / settings
INPUT CONTRACTS
Know what the action needs before it runs.
extract_data
documentUrlREQUIRED- A public URL, presigned URL, reducto:// file identifier, or jobid:// parse job identifier accepted by Reducto.
schemaREQUIRED- JSON Schema object that tells Reducto which fields to extract.
systemPromptOPTIONAL- Optional system prompt used by Reducto extraction.
parsingOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
settingsOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
parse_document
documentUrlREQUIRED- A public URL, presigned URL, reducto:// file identifier, or jobid:// parse job identifier accepted by Reducto.
enhanceOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
retrievalOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
formattingOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
spreadsheetOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
split_document
documentUrlREQUIRED- A public URL, presigned URL, reducto:// file identifier, or jobid:// parse job identifier accepted by Reducto.
splitDescriptionREQUIRED- The Reducto section descriptions to identify in the document.
splitRulesOPTIONAL- Optional prompt that defines global rules for splitting.
parsingOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
settingsOPTIONAL- Reducto configuration object forwarded to the official API using Reducto option names.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Extract Data
Extract structured JSON from a Reducto-supported document URL or file id using a caller-supplied JSON Schema. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
extract_dataVerify with Parse Document
Parse a Reducto-supported document URL or file id into structured chunks, blocks, and document metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
parse_documentSAFETY BOUNDARY
Operate Reducto with explicit limits
- Authorize Reducto with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Reducto data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Reducto rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Reducto task completed successfully.
CONNECTION MODEL
API key
Reducto API key sent with the Authorization Bearer header. Create or manage keys in Reducto Studio: https://studio.reducto.ai/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Reducto.