Connect Cursor

• A Signvoy account with at least one published template.
• Cursor with MCP support (Settings → MCP).

1. Open MCP settings

Go to Cursor Settings → MCP and choose to add a new server. That opens your mcp.json.

2. Add the Signvoy entry

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

3. Authenticate

Cursor will show the server as needing authentication. Click its login control — a browser opens, you sign in to Signvoy, approve the connection, and Cursor stores the token. The server should then show as connected with its tools listed.

Cursor reads MCP config from two places, and for Signvoy the choice matters more than it might seem:

• ~/.cursor/mcp.json — global, available in every project. Recommended for Signvoy. Signing contracts is an account-level capability, not a property of one repository.
• .cursor/mcp.json — project-scoped, and usually committed to git. Fine if your whole team should have the server available, but it means teammates see a signing tool in every session whether they want it or not.

Ask for something read-only in the chat pane:

List my Signvoy templates and tell me which ones are published.

Cursor should call signvoy_list_templates and report which templates have hasPublishedVersion: true. Only those can create documents.

Having signing available inside the editor is most useful when contract state is adjacent to code you are already working on.

# Check on a customer while wiring up their integration
Has Acme signed their MSA yet? If someone is still pending, tell me who.

# Generate an embedded signing link to test your own integration
Create a signing link for the pending recipient on the most recent sent
document, so I can test the embed flow locally.

# Reconcile what your webhook handler saw against Signvoy's own record
Show me the audit trail for document <id> so I can compare it with the
webhook events my handler logged.