Can I use Signnow as a CLI?

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

Can I expose Signnow through MCP?

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

Where are Signnow credentials stored?

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

Can I deny write access for Signnow MCP tools?

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

other

Signnow CLI for AI Agents

Use the Signnow CLI from KosmoKrator to call Signnow tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

6 functions 4 read 2 write Manual OAuth token auth

Submit Signnow feedback View package source

Signnow CLI Setup

Signnow can be configured headlessly with `kosmokrator integrations:configure signnow`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure signnow --set access_token="$SIGNNOW_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor signnow --json
kosmokrator integrations:status --json

Credentials

Authentication type: Manual OAuth token oauth2_manual_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`SIGNNOW_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`SIGNNOW_URL`	URL `url`	no	API Base URL

Call Signnow Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call signnow.signnow_list_documents '{
  "page": 1,
  "per_page": 1
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:signnow signnow_list_documents '{
  "page": 1,
  "per_page": 1
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs signnow --json
kosmo integrations:docs signnow.signnow_list_documents --json
kosmo integrations:schema signnow.signnow_list_documents --json
kosmo integrations:search "Signnow" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Signnow.

`signnow.signnow_list_documents`

Read read

List documents accessible to the authenticated SignNow user. Returns document IDs, names, and status. Supports pagination with page and per_page parameters.

Parameters: page, per_page

Generic CLI call

kosmo integrations:call signnow.signnow_list_documents '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:signnow signnow_list_documents '{"page":1,"per_page":1}' --json

`signnow.signnow_get_document`

Read read

Get full details for a specific SignNow document by ID, including fields, signers, and document status.

Parameters: document_id

Generic CLI call

kosmo integrations:call signnow.signnow_get_document '{"document_id":"example_document_id"}' --json

Provider shortcut

kosmo integrations:signnow signnow_get_document '{"document_id":"example_document_id"}' --json

`signnow.signnow_create_document`

Write write

Upload a file to SignNow to create a new document. The file must be a PDF. Returns the new document ID and details.

Parameters: file_path, file_name

Generic CLI call

kosmo integrations:call signnow.signnow_create_document '{"file_path":"example_file_path","file_name":"example_file_name"}' --json

Provider shortcut

kosmo integrations:signnow signnow_create_document '{"file_path":"example_file_path","file_name":"example_file_name"}' --json

`signnow.signnow_list_templates`

Read read

List document templates available in the authenticated SignNow account. Templates can be used to create new documents with pre-defined fields.

Parameters: none

Generic CLI call

kosmo integrations:call signnow.signnow_list_templates '{}' --json

Provider shortcut

kosmo integrations:signnow signnow_list_templates '{}' --json

`signnow.signnow_send_invite`

Write write

Send a signing invitation for a SignNow document. The recipient will receive an email with a link to review and sign the document.

Parameters: document_id, to, from, subject, message

Generic CLI call

kosmo integrations:call signnow.signnow_send_invite '{"document_id":"example_document_id","to":"example_to","from":"example_from","subject":"example_subject","message":"example_message"}' --json

Provider shortcut

kosmo integrations:signnow signnow_send_invite '{"document_id":"example_document_id","to":"example_to","from":"example_from","subject":"example_subject","message":"example_message"}' --json

`signnow.signnow_get_current_user`

Read read

Get the authenticated SignNow user profile, including name, email, and account details.

Parameters: none

Generic CLI call

kosmo integrations:call signnow.signnow_get_current_user '{}' --json

Provider shortcut

kosmo integrations:signnow signnow_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`signnow.signnow_list_documents`

List documents accessible to the authenticated SignNow user. Returns document IDs, names, and status. Supports pagination with page and per_page parameters.

Operation: Read read
Schema command: kosmo integrations:schema signnow.signnow_list_documents --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (1-based). Default: 1.
`per_page`	integer	no	Number of documents per page. Default: 20.

`signnow.signnow_get_document`

Get full details for a specific SignNow document by ID, including fields, signers, and document status.

Operation: Read read
Schema command: kosmo integrations:schema signnow.signnow_get_document --json

Parameter	Type	Required	Description
`document_id`	string	yes	The unique document identifier.

`signnow.signnow_create_document`

Upload a file to SignNow to create a new document. The file must be a PDF. Returns the new document ID and details.

Operation: Write write
Schema command: kosmo integrations:schema signnow.signnow_create_document --json

Parameter	Type	Required	Description
`file_path`	string	yes	Absolute path to the PDF file to upload.
`file_name`	string	no	Name for the uploaded file. Defaults to the basename of file_path.

`signnow.signnow_list_templates`

List document templates available in the authenticated SignNow account. Templates can be used to create new documents with pre-defined fields.

Operation: Read read
Schema command: kosmo integrations:schema signnow.signnow_list_templates --json

Parameter	Type	Required	Description
No parameters.

`signnow.signnow_send_invite`

Send a signing invitation for a SignNow document. The recipient will receive an email with a link to review and sign the document.

Operation: Write write
Schema command: kosmo integrations:schema signnow.signnow_send_invite --json

Parameter	Type	Required	Description
`document_id`	string	yes	The unique document identifier to send an invite for.
`to`	string	yes	Recipient email address for the signing invite.
`from`	string	yes	Sender email address (must be the authenticated user email).
`subject`	string	yes	Email subject line for the signing invitation.
`message`	string	no	Optional custom message body for the invitation email.

`signnow.signnow_get_current_user`

Get the authenticated SignNow user profile, including name, email, and account details.

Operation: Read read
Schema command: kosmo integrations:schema signnow.signnow_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.