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 MCP Integration for CrewAI

Connect Signnow to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 4 read 2 write Manual OAuth token auth

Submit Signnow feedback View package source

Connect Signnow to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Signnow MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-signnow": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=signnow",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=signnow --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Signnow instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Signnow Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Signnow integration catalog.

MCP tool	Source function	Type	Description
`integration__signnow__signnow_list_documents`	`signnow.signnow_list_documents`	Read	List documents accessible to the authenticated SignNow user. Returns document IDs, names, and status. Supports pagination with page and per_page parameters.
`integration__signnow__signnow_get_document`	`signnow.signnow_get_document`	Read	Get full details for a specific SignNow document by ID, including fields, signers, and document status.
`integration__signnow__signnow_create_document`	`signnow.signnow_create_document`	Write	Upload a file to SignNow to create a new document. The file must be a PDF. Returns the new document ID and details.
`integration__signnow__signnow_list_templates`	`signnow.signnow_list_templates`	Read	List document templates available in the authenticated SignNow account. Templates can be used to create new documents with pre-defined fields.
`integration__signnow__signnow_send_invite`	`signnow.signnow_send_invite`	Write	Send a signing invitation for a SignNow document. The recipient will receive an email with a link to review and sign the document.
`integration__signnow__signnow_get_current_user`	`signnow.signnow_get_current_user`	Read	Get the authenticated SignNow user profile, including name, email, and account details.

Related Signnow Pages

Signnow CLIUse direct JSON commands instead of MCP discovery. Signnow MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.