Ragie MCP integration for AI agents.
Connect AI agents to Ragie through 19 structured actions, including get document, create document from url, delete document, and patch document metadata. Rev…
- ACTION CONTRACTS
- 19
- 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 Ragie integration exposes
The Ragie Agent App exposes 19 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent get a single ragie document by id to inspect status, metadata, errors, and counts, create a ragie document from a public url when the source file is already hosted externally, and delete a ragie document, optionally in asynchronous mode. 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 Ragie account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ragie capabilities.
Showing 12 of 19 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_documentREADGet a single Ragie document by ID to inspect status, metadata, errors, and counts.
INPUTS: documentId / partition
create_document_from_urlWRITECreate a Ragie document from a public URL when the source file is already hosted externally.
INPUTS: url / mode / name / metadata / partition
delete_documentHIGH IMPACTDelete a Ragie document, optionally in asynchronous mode.
INPUTS: documentId / async / partition
patch_document_metadataREVIEWPatch Ragie document metadata in place without replacing the entire metadata object.
INPUTS: documentId / metadata / partition / async
create_document_rawWRITECreate a Ragie document from raw text or JSON data when the content already exists in memory and does not need file upload.
INPUTS: data / name / metadata / partition / externalId
create_oauth_redirect_urlWRITECreate the Ragie embedded OAuth redirect URL for a connection source type such as Google Drive or Notion.
INPUTS: redirectUri / sourceType / theme / config / metadata
create_partitionWRITECreate a Ragie partition to isolate documents, metadata schemas, and resource limits by workspace or tenant.
INPUTS: name / description / contextAware / metadataSchema / mediaHostedLimitMax
delete_partitionHIGH IMPACTDelete a Ragie partition, optionally in asynchronous mode.
INPUTS: partitionId / asyncDeletion
get_document_chunksREADList the chunks of a Ragie document with cursor pagination and optional start/end index filtering.
INPUTS: documentId / cursor / pageSize / partition / startIndex
get_document_contentREADGet Ragie document content in the requested media type, with optional byte range and download behavior.
INPUTS: documentId / range / download / partition / mediaType
get_document_summaryREADGet the Ragie-generated summary for a specific document.
INPUTS: documentId / partition
get_partitionREADGet a specific Ragie partition together with its limits and usage stats.
INPUTS: partitionId
INPUT CONTRACTS
Know what the action needs before it runs.
get_document
documentIdREQUIRED- The document identifier.
partitionOPTIONAL- The partition to scope the request to.
create_document_from_url
urlREQUIRED- The public URL of the source document.
modeOPTIONAL- The optional processing mode for ingestion.
nameOPTIONAL- The user-facing document name.
metadataOPTIONAL- A metadata object containing Ragie-compatible primitive values.
partitionOPTIONAL- The partition to place the document in.
delete_document
documentIdREQUIRED- The document identifier.
asyncOPTIONAL- Whether Ragie should delete the document asynchronously.
partitionOPTIONAL- The partition to scope the request to.
patch_document_metadata
documentIdREQUIRED- The document identifier.
metadataREQUIRED- The metadata fields to upsert or remove with null values.
partitionOPTIONAL- The partition to scope the request to.
asyncOPTIONAL- Whether Ragie should run the metadata patch asynchronously.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Document
Get a single Ragie document by ID to inspect status, metadata, errors, and counts. 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
Create a Ragie document from a public URL when the source file is already hosted externally. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_document_from_urlVerify with Create Document From Url
Create a Ragie document from a public URL when the source file is already hosted externally. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_document_from_urlSAFETY BOUNDARY
Operate Ragie with explicit limits
- Authorize Ragie with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_document` and `delete_partition` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Ragie rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ragie task completed successfully.
CONNECTION MODEL
API key
Ragie API key used with the Authorization Bearer header. Create it by following the official guide at https://docs.ragie.ai/docs/step-1-create-an-api-key.
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
- 10
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 1
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 Ragie.