Inventories templates and images, inspects a template's fields and conditions, reports quota and queue capacity, and clears stale files.
17actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro analyzes a template's parsed structure to understand available fields, repeats, and conditional logic. This informs decisions on data mapping and field population.
Ayro checks the progress of batch template uploads to confirm all documents are ready for generation. Status updates prevent attempting renders on incomplete uploads.
Ayro retrieves the complete list of available templates so customers can browse and select the right format. Template inventory is always current and searchable.
Each card is one request a support team gets, and the Docmosis actions Ayro runs to close it.
Ayro lists the templates in a folder with pagination, returns one template's size, MD5 hash, last modified date, and error status, and downloads the originals when someone needs the source file back.
Ayro returns the parsed structure of a template - its fields, repeats, conditions, images, and refs - generates placeholder data for a test render, and confirms a batch upload actually finished.
Ayro verifies the environment is active and within quota, reads the plan and status summary behind it, and reports current render queue utilisation before a bulk run is scheduled.
Ayro lists the stock images available in a folder, removes images by name, and deletes several obsolete templates in a single request rather than one at a time.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Docmosis actions it has and picks the ones a request needs.
Authorize the Docmosis account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Docmosis actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeDocmosis · Ayro
What can you do in Docmosis without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Docmosis.
Not through this toolkit. Every action here manages templates, images, and the environment: listing, downloading, inspecting structure, generating sample data, deleting, plus readiness and queue checks. There is no render action exposed, so document generation stays with your existing Docmosis integration while Ayro prepares and verifies the templates behind it.
All 17 actions your agent can call on Docmosis, straight from the live MCP connection.
Delete one or more stored images.
Delete one or more templates from the environment.
Verify environment readiness.
Retrieve environment summary.
Extract the Docmosis API access key from connection metadata.
Check the status of a template batch upload job.
Download one or more images.
Get current render queue status and utilization.
Retrieve statistics on renders tagged with user-defined phrases.
Generate sample data for a Docmosis template based on its structure.
Retrieve originally uploaded templates.
Retrieve metadata for an uploaded template.
Retrieve a template's parsed structure: fields, repeats, conditions, images, and refs.
List available stock images.
List all templates available in the environment.
Check connectivity to Docmosis Cloud services.
Check that Docmosis Cloud services are online and at least one server is listening.
Same connection, same setup. Pick the next one your team already uses.
Lists the extractors configured on an account with their IDs, returns the folder hierarchy, and confirms which AlgoDocs user the key belongs to.
Uploads a file, runs the conversion, polls the task until it finishes, and returns the download link without anyone opening the dashboard.
Confirms the connected account, lists existing workspace folders, and creates the folder a set of generated documents should land in.
Configures extraction and classification jobs, retrieves batch results with their processing status, and clears jobs and credits down after.
Searches file contents for the document someone means, files attachments into the right folder, issues scoped sharing links, and restores deleted items.
Runs GROQ queries and fetches documents by ID, audits project roles and service accounts, and manages custom user attributes.

Authorize the account and your agent has all 17 actions from the first conversation.
