Signvoy logoSignvoy

MCP Client Setup

Connect Claude

Give Claude one URL and approve a browser consent screen. From then on you can ask Claude to draft contracts from your templates, send them for signature, chase pending signers, and fetch the completed PDF.

No API key
No client secret
One-time consent

Prerequisites

  • A Signvoy account with at least one published template. Drafts cannot be used to create documents — publish the template first.
  • Claude Desktop, or Claude Code, on a plan that allows custom MCP servers.
  • Nothing else. There is no key to generate and no application to register on the Signvoy side.
Coming from another platform? Some e-signature vendors require you to create an integration key, generate a client secret, and paste Claude's OAuth callback URLs into your app settings before connecting. Signvoy supports Dynamic Client Registration, so Claude does all of that itself.

Claude Desktop

Signvoy is a remote server, so it is added through Connectors rather than through a config file. There is no JSON to edit and nothing to install.

Not claude_desktop_config.json. That file is for local stdio servers that Claude launches as a subprocess. Putting a remote url in it will not connect.

1. Open Connectors

Go to Settings → Connectors and choose Add custom connector.

2. Point it at Signvoy

Name it Signvoy and paste the endpoint as the URL:

server URL
https://api.signvoy.com/mcp

Leave the OAuth client set to register automatically. Signvoy supports Dynamic Client Registration, so there is no client ID or secret to fill in.

3. Connect and consent

Click Add, then Connect. A browser window opens asking you to sign in to Signvoy and approve the connection. Approve it once and Claude stores the token.

Authentication settings cannot be changed after a connector is added — if you pick the wrong option, remove the connector and add it again. On Team and Enterprise plans an owner adds the connector once under Organization settings, and each member then connects with their own account. See troubleshooting if it fails to connect.

Claude Code

Claude Code can add the server from the command line. This registers it for the current project:

terminal
claude mcp add --transport http signvoy https://api.signvoy.com/mcp

To make it available in every project, add it at user scope instead:

terminal
claude mcp add --transport http --scope user signvoy https://api.signvoy.com/mcp

Then run /mcp inside Claude Code to see connection status and trigger the consent flow.

Verify the connection

Ask Claude a read-only question first. It exercises auth without touching any document:

prompt
List my Signvoy workspaces.

Claude should call signvoy_list_workspaces and come back with your workspace names, slugs, and your role in each. If that works, auth is correct and every other tool will work too.

Things to try

Start read-only, then move to sending once you trust the flow. The prompt library has more, with notes on what makes each one reliable.

prompts
# Read-only — safe to run immediately
Which of my Signvoy documents are still waiting on signatures, and who is holding each one up?

Show me the audit trail for the most recent completed document.

# Creates a draft, sends nothing
Draft an NDA from my "Mutual NDA" template for Dana Kim at dana@example.com.
Show me the review link before doing anything else.

# Sends real email — Claude should confirm with you first
That draft looks right. Send it.
Sending is not reversible. Once signvoy_send_document runs, recipients receive email. Voiding a document afterwards revokes the signing links but cannot unsend the notification.

FAQ

Can Claude send a document for signature?

Yes. Once the Signvoy MCP server is connected, you can ask Claude in plain language to create a document from one of your templates and send it for signature. Claude creates a draft first and shows you the recipient list and a review link; a separate confirmed step is what actually emails recipients.

Do I need a paid Claude plan?

You need a Claude plan that supports connectors or custom MCP servers. Claude Desktop and Claude Code both support remote MCP servers over streamable HTTP, which is what Signvoy exposes.

Where do I put my Signvoy API key for Claude?

Nowhere. The Signvoy MCP server uses OAuth 2.1 with Dynamic Client Registration, so Claude registers itself and obtains a token through a browser consent screen. There is no API key or client secret to enter anywhere in Claude.

Why does a browser window open the first time Claude connects?

That is the OAuth consent screen. You sign in to Signvoy and approve the connection once; Claude stores the resulting token and reuses it. You will not be prompted again unless you revoke the grant.

How do I disconnect Claude from Signvoy?

Remove the connector in Claude Desktop, or run claude mcp remove signvoy in Claude Code, to stop Claude using it. Then revoke the grant server-side so the stored token can no longer be used — either under Workspace Settings → AI Agents in the dashboard, or with DELETE /v1/mcp-grants/:id. Each client has its own grant, so revoking Claude does not affect Cursor.

Deja de perseguir firmas

Únete a miles de equipos que usan Signvoy para cerrar acuerdos, incorporar clientes y firmar contratos, más rápido.

Crea tu cuenta gratuita
Iniciar sesión

Sin tarjeta de crédito · Plan gratuito para siempre · Cancela cuando quieras