Xodo Sign MCP integration for AI agents.
Connect AI agents to Xodo Sign through 9 structured actions, including get audit log, create document, and reassign signer. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 9
- 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 Xodo Sign integration exposes
The Xodo Sign Agent App exposes 9 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent retrieve the complete audit event history for a xodo sign document, create an xodo sign document from public file urls or existing xodo sign file ids, and replace a signer on a xodo sign document and notify the affected participants. 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 Xodo Sign account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Xodo Sign capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_audit_logREADRetrieve the complete audit event history for a Xodo Sign document.
INPUTS: businessId / documentHash
create_documentWRITECreate an Xodo Sign document from public file URLs or existing Xodo Sign file IDs.
INPUTS: businessId / files / signers / recipients / isDraft
reassign_signerREVIEWReplace a signer on a Xodo Sign document and notify the affected participants.
INPUTS: businessId / documentHash / signerId / newSignerName / newSignerEmail
create_document_from_templateWRITECreate an Xodo Sign document from an existing template, role assignments, and merge fields.
INPUTS: businessId / templateId / signers / recipients / mergeFields
get_documentREADRetrieve an Xodo Sign document or template by its document hash.
INPUTS: businessId / documentHash
list_businessesREADList businesses available to the connected Xodo Sign API key.
list_documentsREADList Xodo Sign documents for a business, optionally filtering by documented status.
INPUTS: businessId / type / limit / page
list_templatesREADList active, archived, or draft Xodo Sign templates for a business.
INPUTS: businessId / type / limit / page
send_reminderWRITESend a reminder to one signer of a Xodo Sign document.
INPUTS: businessId / documentHash / signerId
INPUT CONTRACTS
Know what the action needs before it runs.
get_audit_log
businessIdREQUIRED- The Xodo Sign business ID.
documentHashREQUIRED- The Xodo Sign document or template hash.
create_document
businessIdREQUIRED- The Xodo Sign business ID.
filesREQUIRED- Files to include in the document.
signersREQUIRED- People required to sign the document.
recipientsOPTIONAL- Non-signing recipients who receive document notifications.
isDraftOPTIONAL- Whether to save the document as a draft without sending it.
reassign_signer
businessIdREQUIRED- The Xodo Sign business ID.
documentHashREQUIRED- The Xodo Sign document or template hash.
signerIdREQUIRED- The signer ID to replace.
newSignerNameREQUIRED- The replacement signer's full name.
newSignerEmailREQUIRED- The replacement signer's email address.
create_document_from_template
businessIdREQUIRED- The Xodo Sign business ID.
templateIdREQUIRED- The document hash of the Xodo Sign template to use.
signersREQUIRED- Signer assignments for required template roles.
recipientsOPTIONAL- Recipient assignments for template CC roles.
mergeFieldsOPTIONAL- Values for merge fields defined by the template.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Audit Log
Retrieve the complete audit event history for a Xodo Sign document. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_audit_logControl Create Document
Create an Xodo Sign document from public file URLs or existing Xodo Sign file IDs. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_documentVerify with Get Document
Retrieve an Xodo Sign document or template by its document hash. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_documentSAFETY BOUNDARY
Operate Xodo Sign with explicit limits
- Authorize Xodo Sign with API key and grant only the provider access required by the selected actions.
- 3 actions are 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 Xodo Sign rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Xodo Sign task completed successfully.
CONNECTION MODEL
API key
Xodo Sign API access key sent as the access_key query parameter. In your Xodo Sign account, open the top-left menu and select Developer to view or reset it: https://support.apryse.com/support/solutions/articles/35000297407-api-frequently-asked-questions
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
- 3
- 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 Xodo Sign.