Affinda MCP integration for AI agents.
Connect AI agents to Affinda through 6 structured actions, including get document, create document from url, and list document types. Review authentication…
- 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 Affinda integration exposes
The Affinda Agent App exposes 6 provider-backed actions for ai and data work. Its current contract lets an authorized agent get one affinda document by identifier, upload a document to affinda from a url and optionally wait for parsing results, and list affinda document types available to the 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 Affinda account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Affinda capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_documentREADGet one Affinda document by identifier.
INPUTS: identifier / compact
create_document_from_urlWRITEUpload a document to Affinda from a URL and optionally wait for parsing results.
INPUTS: url / workspace / documentType / wait / customIdentifier
list_document_typesREADList Affinda document types available to the API key.
INPUTS: organization / workspace
list_documentsREADList Affinda documents with optional workflow and pagination filters.
INPUTS: offset / limit / workspace / state / tags
list_organizationsREADList Affinda organizations available to the connected API key.
list_workspacesREADList Affinda workspaces in an organization.
INPUTS: organization / name
INPUT CONTRACTS
Know what the action needs before it runs.
get_document
identifierREQUIRED- The Affinda document identifier.
compactOPTIONAL- Whether Affinda should return compact parsed data.
create_document_from_url
urlREQUIRED- The publicly reachable document URL for Affinda to download and parse.
workspaceREQUIRED- The Affinda workspace identifier to upload the document to.
documentTypeOPTIONAL- The Affinda document type identifier when the document type is already known.
waitOPTIONAL- Whether Affinda should wait for parsing to complete before responding.
customIdentifierOPTIONAL- An optional user-defined identifier for tracking the document in Affinda.
list_document_types
organizationOPTIONAL- Filter document types by Affinda organization identifier.
workspaceOPTIONAL- Filter document types by Affinda workspace identifier.
list_documents
offsetOPTIONAL- The number of documents to skip before collecting results.
limitOPTIONAL- The number of documents to return.
workspaceOPTIONAL- Filter by Affinda workspace identifier.
stateOPTIONAL- Filter by the Affinda document state.
tagsOPTIONAL- Filter by Affinda tag IDs.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Document
Get one Affinda document by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_documentControl Create Document From Url
Upload a document to Affinda from a URL and optionally wait for parsing results. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_document_from_urlVerify with List Document Types
List Affinda document types available to the API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_document_typesSAFETY BOUNDARY
Operate Affinda with explicit limits
- Authorize Affinda 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 Affinda rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Affinda task completed successfully.
CONNECTION MODEL
API key
Affinda API key sent as a Bearer token. Create and rotate keys from your Affinda user settings: https://docs.affinda.com/reference/authentication.
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 Affinda.