BoldSign MCP integration for AI agents.
Connect AI agents to BoldSign through 6 structured actions, including get api credits, send document from template, and get document details. Review authenti…
- 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 BoldSign integration exposes
The BoldSign Agent App exposes 6 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent get the remaining boldsign api document credits for the connected account, send a boldsign signature request from an existing template and return the new document id, and get the status, signers, and full json details for one boldsign document. 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 BoldSign account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BoldSign capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_creditsREADGet the remaining BoldSign API document credits for the connected account.
send_document_from_templateWRITESend a BoldSign signature request from an existing template and return the new document ID.
INPUTS: templateId / title / message / roles / fileUrls
get_document_detailsREADGet the status, signers, and full JSON details for one BoldSign document.
INPUTS: documentId
get_template_detailsREADGet roles, files, and full JSON details for one BoldSign template.
INPUTS: templateId
list_documentsREADList BoldSign documents available to the connected account with filters and pagination.
INPUTS: page / pageSize / sentBy / recipients / transmitType
list_templatesREADList BoldSign templates available to the connected account with filters and pagination.
INPUTS: page / pageSize / templateType / searchKey / onBehalfOf
INPUT CONTRACTS
Know what the action needs before it runs.
send_document_from_template
templateIdREQUIRED- The existing BoldSign template identifier.
titleOPTIONAL- The title shown in BoldSign and signature request emails.
messageOPTIONAL- A message sent to all recipients.
rolesOPTIONAL- Template roles mapped to real signers.
fileUrlsOPTIONAL- Public file URLs added when the template permits new files. BoldSign fetches these URLs.
get_document_details
documentIdOPTIONAL- The BoldSign document identifier.
get_template_details
templateIdOPTIONAL- The BoldSign template identifier.
list_documents
pageOPTIONAL- The page number to return. Defaults to 1.
pageSizeOPTIONAL- The number of records to return per page.
sentByOPTIONAL- Sender email addresses to include.
recipientsOPTIONAL- Recipient email addresses to include.
transmitTypeOPTIONAL- Whether to include sent, received, or both document sets.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Credits
Get the remaining BoldSign API document credits for the connected account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_creditsControl Send Document From Template
Send a BoldSign signature request from an existing template and return the new document ID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_document_from_templateVerify with Get Document Details
Get the status, signers, and full JSON details for one BoldSign document. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_document_detailsSAFETY BOUNDARY
Operate BoldSign with explicit limits
- Authorize BoldSign 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 BoldSign rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BoldSign task completed successfully.
CONNECTION MODEL
API key
Generate a BoldSign API key from API > API Key: https://developers.boldsign.com/authentication/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
- 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 BoldSign.