Model Context Protocol

AI agents.

Signvoy runs an official MCP server, so Claude, Cursor, and any other MCP-compatible assistant can draft contracts, send them for signature, chase pending signers, and fetch the completed PDF — all from a conversation.

No API key
One-time approval
Claude and Cursor
Works on the free plan

The entire setup

{
  "mcpServers": {
    "signvoy": {
      "url": "https://api.signvoy.com/mcp"
    }
  }
}

Paste this into your assistant's MCP config. There is no key to generate and no secret to store.

What your assistant can do

Each capability maps to a real tool on the server, not a prompt trick. Ask in plain language and your assistant picks the right one.

Draft from a template

Turn any published Signvoy template into a document, with recipients assigned to the right roles.

“Draft an NDA from my Mutual NDA template for Dana at dana@example.com.”

Send for signature

Email signing requests once you have reviewed the draft. Always a separate, confirmed step.

“That draft looks right — send it.”

Track who has signed

Read across every open document and see which recipient is holding each one up.

“Which documents are still waiting on signatures, and who hasn't signed?”

Chase pending signers

Send a reminder to recipients who have not signed yet, on the documents you choose.

“Remind everyone still pending on the Acme MSA.”

Collect the signed PDF

Get a short-lived download link for the certified PDF once every recipient has signed.

“The Acme MSA is done — get me the signed copy.”

Read the audit trail

Pull the append-only event log for a document and have it summarised as a timeline.

“Summarise the audit trail for the Acme MSA.”

16 tools in total, including embedded signing links and document voiding. See the full tool reference

Why Signvoy for agents

Letting software send contracts on your behalf is a trust problem before it is an integration problem. Three things we do differently.

No API key to leak

Most e-signature MCP servers ask you to paste a static API key into a config file. Signvoy uses OAuth 2.1 with Dynamic Client Registration: your assistant registers itself, you approve once in the browser, and nothing long-lived is written to disk.

A human approves every send

Drafting and sending are separate tools. Creating a document returns a review link and emails nobody; a second confirmed step is what reaches your counterparty. An agent cannot collapse the two.

Agent actions are labelled

Every change an assistant makes is written to the same tamper-evident audit trail as dashboard activity, tagged as agent-initiated alongside the user, IP address, and timestamp.

How it works

Three steps, once.

1

Add one URL

Paste the Signvoy server into your assistant's MCP config. No package to install and nothing to run locally.

2

Approve in the browser

Your assistant discovers Signvoy's authorization server and registers itself. You sign in and approve the connection one time.

3

Just ask

The signing tools are now available. Ask for what you want in plain language and your assistant picks the right ones.

Works with your assistant

Any client that supports remote MCP servers over streamable HTTP can connect. Pick yours for the exact setup — the key names genuinely differ between them.

One entry in mcp.json. Nothing to install.

Add to Cursor

Manual setup

  1. Open Customize → MCPs in the Cursor sidebar, or edit the config file directly.

  2. Add Signvoy to your global config so it is available in every project. Use .cursor/mcp.json in a project folder instead if you only want it there.

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "signvoy": {
          "url": "https://api.signvoy.com/mcp"
        }
      }
    }
  3. Restart Cursor, then click the server's authenticate control. A browser opens for you to sign in and approve the connection.

Full Cursor guide

Each snippet uses that client's own key names. Copying another client's block is the usual reason a server shows up as disconnected.

FAQ

Still curious? Email support@signvoy.com.

The assistant does not sign — it prepares and sends. Signatures are still collected from the named human recipients through Signvoy's normal signing flow, which is legally binding under the ESIGN Act, UETA, and eIDAS. What the assistant automates is the administrative work around the signature, not the signature itself.

Stop chasing signatures

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

No credit card · Free forever plan · Cancel anytime