Docmosis MCP integration for AI agents.
Connect AI agents to Docmosis through 6 structured actions, including check environment ready, render document, and get environment summary. Review authentic…
- 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 Docmosis integration exposes
The Docmosis Agent App exposes 6 provider-backed actions for productivity and design & media work. Its current contract lets an authorized agent check whether the selected docmosis environment is currently ready to service render requests, render one docmosis template with json data and return json-safe delivery metadata or an explicit base64 result file, and get docmosis environment plan, quota, and readiness information for the selected processing location. 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 Docmosis account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Docmosis capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_environment_readyREADCheck whether the selected Docmosis environment is currently ready to service render requests.
render_documentREVIEWRender one Docmosis template with JSON data and return JSON-safe delivery metadata or an explicit base64 result file.
INPUTS: templateName / outputName / data / outputFormat / storeTo
get_environment_summaryREADGet Docmosis environment plan, quota, and readiness information for the selected processing location.
get_template_detailsREADGet the stored metadata for one uploaded Docmosis template without downloading the template file.
INPUTS: templateName
get_template_structureREADGet the Docmosis template structure tree that describes fields, repeats, conditions, and other data references.
INPUTS: templateName
list_templatesREADList Docmosis templates available in the selected processing location with optional folder and paging controls.
INPUTS: includeDetail / folder / includeSubFolders / paging / pageToken
INPUT CONTRACTS
Know what the action needs before it runs.
render_document
templateNameREQUIRED- The Docmosis template path to render.
outputNameREQUIRED- The output filename including the preferred extension.
dataREQUIRED- The JSON data payload merged into the template.
outputFormatOPTIONAL- The optional output format override.
storeToOPTIONAL- The optional Docmosis delivery target such as `mailto:person@example.com` or `s3:bucket,key`.
get_template_details
templateNameOPTIONAL- The template path to inspect.
get_template_structure
templateNameOPTIONAL- The template path to inspect.
list_templates
includeDetailOPTIONAL- Whether to include extra template detail such as template error status.
folderOPTIONAL- The optional starting folder path to list.
includeSubFoldersOPTIONAL- Whether template results should include templates inside sub-folders.
pagingOPTIONAL- Whether Docmosis should return paged results.
pageTokenOPTIONAL- The pagination token previously returned by Docmosis.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Environment Ready
Check whether the selected Docmosis environment is currently ready to service render requests. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_environment_readyVerify with Get Environment Summary
Get Docmosis environment plan, quota, and readiness information for the selected processing location. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_environment_summarySAFETY BOUNDARY
Operate Docmosis with explicit limits
- Authorize Docmosis with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Docmosis 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 Docmosis rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Docmosis task completed successfully.
CONNECTION MODEL
API key
Docmosis environment access key used to authenticate Cloud API requests. Create or copy it from your environment API Keys page in the Cloud Console: https://resources.docmosis.com/content/faq/where-are-my-api-keys-and-base-urls-for-my-environments
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
- 0
- HIGH IMPACT
- 0
- 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 Docmosis.