Signvoy

Most e-signature MCP servers ask you to generate a credential and paste it into a config file. Some also require you to register an application and copy your AI client's OAuth redirect URIs into it before anything works.

Signvoy implementsOAuth 2.1 with Dynamic Client Registration, so your client does that work itself. You paste a URL; the client discovers the authorization server, registers, and opens a browser for you to consent. Nothing long-lived is ever written to a config file on disk.

Why this matters:a static API key inclaude_desktop_config.jsonis a plaintext secret with no expiry, sitting in a file that AI agents can often read. An OAuth grant is scoped to one client, revocable on its own, and carries no secret you could leak by sharing your config.

Add this to your MCP client's config. It is the same block for every client:

{ "mcpServers": { "signvoy": { "url": "https://api.signvoy.com/mcp", "transport": "streamable-http" } } }

You do not need to understand this to use the server — your client handles all five steps. It is documented because knowing the flow makes failures easy to read.

List every workspace the authenticated user belongs to.

List templates in a workspace. Defaults to active (non-archived).

Get one template in full, including its recipient role keys.

List documents newest-first, with status filter and text search.

Per-recipient signing state for one document.

Append-only event log for chain-of-custody verification.

Presigned download URL for the certified signed PDF.

Create a draft document from a published template.

Fix a draft before sending — recipients, name, message, or routing mode.

Email signing requests to every recipient.

Send one reminder email to all pending recipients.

signvoy_create_signing_linkwriteidempotent

Embedded signing URL for one pending recipient, no login required.

Irreversibly void a document and revoke all signing links.

An OAuth token identifies auser, not a workspace. Every tool accepts an optionalworkspace_id. If you omit it, Signvoy falls back to the workspace bound to your OAuth grant, which is set to the first workspace your account joined at the time the grant was created.

If you belong to more than one workspace,ask your assistant to “list my Signvoy workspaces” before starting a signing workflow and passworkspace_idexplicitly. It avoids acting on the wrong workspace mid-task.

Sending a contract is irreversible in a way that most agent actions are not. Four properties of the server are designed around that.

Create and send are separate tools—signvoy_create_documentonly produces a draft and hands back areview_url. Nothing is emailed until a second, explicitsignvoy_send_documentcall. An agent cannot conflate the two into a single step.

Destructive actions are annotated—signvoy_void_documentcarries the MCPdestructiveHint, so well-behaved clients prompt before calling it.

Every action is attributed— mutating calls write an audit event taggedactorSource: "mcp"with your user ID, IP address, and user agent. Agent activity is distinguishable from dashboard activity insignvoy_get_audit_trail.

One revocable grant per client— each client that connects gets its own workspace-scoped grant. Revoking one leaves the others working, and there is no static secret to rotate.

Human in the loop:real emails reach real counterparties. Confirm the document name and recipient list before allowingsignvoy_send_document, and be deliberate about running an agent fully unattended — a prompt-injected document could otherwise influence what gets sent.

Grants are managed over the API for now: list them withGET /v1/mcp-grantsand revoke one withDELETE /v1/mcp-grants/:id, using a dashboard session or API key. A grants screen in the dashboard is not available yet.

Do I need an API key to use the Signvoy MCP server?

No. Signvoy uses OAuth 2.1 with Dynamic Client Registration, so your MCP client registers itself and obtains a token through a browser consent screen. You paste one URL into your client config — there is no key to create, no client secret to generate, and no redirect URI to configure.

Which AI clients can connect to Signvoy?

Any client that speaks MCP over streamable HTTP, including Claude Desktop, Claude Code, and Cursor. Signvoy implements the standard OAuth discovery documents, so clients that support remote MCP servers work without a Signvoy-specific plugin.

Can an AI agent send a contract without my approval?

Creating and sending are separate tools. signvoy_create_document only produces a draft and returns a review_url for a human to open; a second explicit call to signvoy_send_document is what actually emails recipients. The bundled signvoy_send_for_signature prompt instructs the model never to skip that review step.

How many tools does the Signvoy MCP server expose?

13 tools: 7 read tools for listing templates and documents, checking per-recipient status, reading the audit trail, and downloading signed PDFs, plus 6 write tools for creating, updating, sending, reminding, generating embedded signing links, and voiding.

Is agent activity recorded in the audit trail?

Yes. Every mutating tool call writes an audit event tagged actorSource: "mcp" along with your user ID, IP address, and user agent, so actions taken by an AI agent are distinguishable from actions taken in the dashboard.

An OAuth token identifies a user, not a workspace. Every tool accepts an optional workspace_id, and omitting it falls back to the workspace bound to your OAuth grant. If you belong to more than one workspace, call signvoy_list_workspaces and pass workspace_id explicitly.

Claude Desktop and Claude Code, step by step

Project and global mcp.json configuration

All 13 tools with parameters and return shapes

Error codes, rate limits, and grant problems

The OAuth discovery document this server advertises