Signvoy logoSignvoy
Automation

6 articles tagged “Automation”. Browse all articles →

workflowautomation

Why Create and Send Should Be Two Different MCP Tools

A single send_contract tool is the most tempting mistake in agent tool design. Splitting the irreversible half into its own call is what keeps a misread instruction from reaching a counterparty's inbox.

September 5, 2026Read
automationmcp

MCP or REST API: Which Should Your Agent Sign With?

Signvoy ships both an MCP server and a REST API, and they are not competing implementations. Which one fits depends on a single question: is a human present when the contract goes out?

September 5, 2026Read
e-signatureworkflow

How to Sign and Send Documents with Claude

Connect Claude to Signvoy's MCP server and send contracts for signature from a conversation. No API key, no plugin — one URL and a consent click.

July 28, 2026Read
automationmcp

Send a Contract for Signature from Cursor

Add Signvoy's MCP server to Cursor and send contracts for signature without leaving your editor. Project vs global mcp.json, verification, and the workflows worth having.

July 22, 2026Read
automationmcp

Build an AI Agent That Sends Contracts

A working architecture for an agent that drafts and routes contracts: the MCP server for the conversational half, @signvoy/node and webhooks for the deterministic half.

July 21, 2026Read
workflowautomation

Automatic Signing Reminders: When to Send Them

Most unsigned documents are forgotten, not rejected. How automatic reminders work, when to send them, and how to set a schedule that lifts completion.

July 4, 2026Read

Stop chasing signatures

Join thousands of teams using Signvoy to close deals, onboard clients, and sign contracts — faster.

Create your free account
Sign in

No credit card · Free forever plan · Cancel anytime