SignNow MCP server icon

SignNow

by SignNow

Productivity16 tools

Send documents for electronic signature, mint embedded signing links and track invite status from your AI assistant. Two tools email a binding signature request on the call; six mint an expiring link instead and send nothing.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect SignNow via MCP

https://mcp-server.signnow.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

SignNow Tools & Capabilities (16)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Two tools email third parties on the call, with no confirmation gate. send_invite and send_invite_from_template have no draft, dry-run or hold parameter in the source. Your MCP client's approval prompt is the only gate.
  • Neither sending tool is annotated destructive. Only update_document_fields carries destructiveHint: true, so clients keying warnings off that hint will not flag a send.
  • No cancel tool among the listed sixteen. SignNow's current release ships one, but the directory surface omits it — and cancelling never recalls delivered email or undoes a completed signature.
  • Embedded signing links default to no signer authentication. auth_method defaults to none, making a minted link a bearer credential. Set it deliberately.
  • The directory snapshot reflects a superseded release. Sixteen listed tools match the v1.0.1 manifest; the current release is v3.1.0 with roughly twenty-five. Treat the count as a floor and call tools/list after connecting.
  • The OAuth scope is a wildcard. scopes_supported is offline_access and *, so access cannot be narrowed to reads and consent is all-or-nothing.
  • We did not run a live tools/list. The endpoint requires OAuth and this catalogue does not authenticate, so the tool inventory here comes from the directory snapshot and SignNow's public source, not from a handshake.

Frequently asked questions

Does the SignNow MCP server actually email signature requests?

Yes, two of its tools do. `send_invite` and `send_invite_from_template` build a per-recipient email with subject and message, then call SignNow's invite endpoints, which dispatch immediately. The open-source implementation exposes no draft flag, no dry-run parameter and no hold-for-approval option, so a caller cannot request staged behaviour. One call puts mail in a signer's inbox.

Do the embedded SignNow tools send email to signers?

No, and that is the connector's best design decision. The six `create_embedded_*` tools mint a signing, sending or editing URL and hand it back to the caller rather than mailing anyone. SignNow documents embedded signing as creating a session without sending an email. One caveat: the embedded invite tool accepts a delivery parameter that can be switched to email.

Can you cancel a SignNow signature request through MCP?

Not through the sixteen tools Anthropic's directory lists, which contain no cancel operation. SignNow's open-source server does implement a cancel tool that voids all pending invites on a document, and its documentation describes that capability, but it sits outside the listed surface. Cancelling stops pending signers; it does not recall email already delivered or undo completed signatures.

Do SignNow embedded signing links expire or require a login?

They expire by default and authentication is optional. The embedded sending and editor tools take a link-lifetime parameter defaulting to fifteen minutes in SignNow's API, with sending capped at forty-five minutes. The embedded invite recipient carries an authentication method that defaults to none, so a minted signing link is a bearer credential unless you set it deliberately.

How many tools does the SignNow MCP server expose?

Anthropic's snapshot lists sixteen and those sixteen match SignNow's version 1.0.1 manifest exactly. The current open-source release is version 3.1.0, whose documentation describes roughly twenty-five tools including cancel, reminder, contact search, upload and rename. The listed sixteen are registered as the version 1.0 compatibility layer, so the snapshot reflects a superseded release.

Are documents signed through SignNow legally binding?

SignNow states its default electronic signature qualifies under both the ESIGN Act and UETA, and that an electronic signature cannot be denied enforceability solely for being electronic. It describes maintaining an audit log for each signing session to support attribution in disputes. Treat that as the vendor's stated position and consult a lawyer about your own use.

What SignNow plan do you need for the MCP server?

SignNow's documentation points at a free developer account rather than a paid tier. Its prerequisites list an account, an active SignNow API application, and credentials comprising an account email, password and application authorization token. No admin enablement switch is documented for the hosted endpoint, which authenticates by OAuth instead of the token-based local setup.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Productivity
Developer
SignNow
Tools
16
Domain
mcp-server.signnow.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.