Can I use Docusign as a CLI?

Yes. KosmoKrator exposes a Docusign CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Docusign through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Docusign tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Docusign credentials stored?

Docusign credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Docusign MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Docusign CLI for Headless Automation

Use the Docusign CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

8 functions 7 read 1 write Manual OAuth token auth

Submit Docusign feedback View package source

Docusign CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Docusign CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Docusign CLI for Headless Automation
kosmokrator integrations:configure docusign --set access_token="$DOCUSIGN_ACCESS_TOKEN" --set account_id="$DOCUSIGN_ACCOUNT_ID" --set base_path="$DOCUSIGN_BASE_PATH" --enable --read allow --write ask --json
kosmo integrations:call docusign.docusign_list_envelopes '{"status":"example_status","from_date":"example_from_date","to_date":"example_to_date","search_text":"example_search_text","count":1,"start_position":1,"order":"example_order","order_by":"example_order_by"}' --json

Discovery Before Execution

Agents and scripts can inspect Docusign docs and schemas before choosing a function.

kosmo integrations:docs docusign --json
kosmo integrations:docs docusign.docusign_list_envelopes --json
kosmo integrations:schema docusign.docusign_list_envelopes --json
kosmo integrations:search "Docusign" --json
kosmo integrations:list --json

Useful Docusign CLI Functions

Function	Type	Parameters	Description
`docusign.docusign_list_envelopes`	Read	status, from_date, to_date, search_text, count, start_position, order, order_by	List envelopes in the DocuSign account. Filter by status (sent, delivered, completed, signed, declined, voided), date range, or search text. Returns envelope summaries with IDs, subjects, statuses, and dates.
`docusign.docusign_get_envelope`	Read	envelope_id, include	Get detailed information about a DocuSign envelope including status, recipients, documents, and signing history. Use this to check if an envelope has been signed or to review its details.
`docusign.docusign_create_envelope`	Write	envelope_definition	Create a new DocuSign envelope for electronic signature. You can create from a template (pass template_id) or from scratch with inline documents and recipients. Set status to "sent" to send immediately or "created" to save as a draft.
`docusign.docusign_list_templates`	Read	search_text, count, start_position, folder_id, folder_ids, order, order_by	List templates available in the DocuSign account. Templates define reusable envelope structures with pre-configured documents, recipients, and signing tabs. Use a template ID to create envelopes from a template.
`docusign.docusign_get_template`	Read	template_id	Get details for a DocuSign template including its documents, recipient roles, signing tabs, and email settings. Use this to understand a template before creating an envelope from it.
`docusign.docusign_list_documents`	Read	envelope_id	List documents in a DocuSign envelope. Returns document IDs, names, types (content or summary), and page counts. Use document IDs to download individual documents.
`docusign.docusign_get_document`	Read	envelope_id, document_id	Download a document from a DocuSign envelope. Returns the document content as base64-encoded data. Use "combined" as the document_id to download all documents as a single combined PDF.
`docusign.docusign_get_current_user`	Read	none	Get information about the authenticated DocuSign user, including name, email, and associated accounts. Useful for verifying credentials and discovering account IDs.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Docusign CLI Pages

CI Docusign CLI for CI. Cron Jobs Docusign CLI for cron jobs. Shell Scripts Docusign CLI for shell scripts. Coding Agents Docusign CLI for coding agents.