AlgoDocs MCP integration for AI agents.
Connect AI agents to AlgoDocs through 6 structured actions, including get extracted data by document, upload document from url, and get me. Review authentica…
- ACTION CONTRACTS
- 6
- 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 AlgoDocs integration exposes
The AlgoDocs Agent App exposes 6 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get extracted data records for one algodocs document id, import a publicly accessible document url into algodocs for an extractor and folder, and get the algodocs account identity for the connected api key. 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 AlgoDocs account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AlgoDocs capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_extracted_data_by_documentREADGet extracted data records for one AlgoDocs document ID.
INPUTS: documentId
upload_document_from_urlWRITEImport a publicly accessible document URL into AlgoDocs for an extractor and folder.
INPUTS: extractorId / folderId / fileUrl
get_meREADGet the AlgoDocs account identity for the connected API key.
list_extracted_dataREADList extracted data records for an AlgoDocs extractor, optionally filtered by folder, limit, and upload date.
INPUTS: extractorId / folderId / limit / date
list_extractorsREADList document data extractors in the connected AlgoDocs account.
list_foldersREADList folders in the connected AlgoDocs file manager.
INPUT CONTRACTS
Know what the action needs before it runs.
get_extracted_data_by_document
documentIdOPTIONAL- The AlgoDocs document ID returned by document import.
upload_document_from_url
extractorIdOPTIONAL- The AlgoDocs resource ID.
folderIdOPTIONAL- The AlgoDocs resource ID.
fileUrlOPTIONAL- The publicly accessible document URL that AlgoDocs should fetch.
list_extracted_data
extractorIdREQUIRED- The AlgoDocs resource ID.
folderIdOPTIONAL- The AlgoDocs resource ID.
limitOPTIONAL- The maximum number of extracted data records to return.
dateOPTIONAL- Only return records uploaded after this AlgoDocs local ISO 8601 combined date-time, for example 2017-06-21T10:45:52.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Extracted Data By Document
Get extracted data records for one AlgoDocs document ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_extracted_data_by_documentControl Upload Document From Url
Import a publicly accessible document URL into AlgoDocs for an extractor and folder. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
upload_document_from_urlVerify with Get Me
Get the AlgoDocs account identity for the connected API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_meSAFETY BOUNDARY
Operate AlgoDocs with explicit limits
- Authorize AlgoDocs with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 AlgoDocs rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AlgoDocs task completed successfully.
CONNECTION MODEL
API key
AlgoDocs secret API key sent with the x-api-key header. Create or view it from your AlgoDocs REST API settings page: https://app.algodocs.com/restapi.
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
- 5
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 AlgoDocs.