NextSign API
Getting Started

Overview

Let your AI assistant create and send NextSign signing cases for you — connect once, then just ask in plain language.

NextSign has an MCP server — a small add-on that connects NextSign to AI assistants like Claude and ChatGPT. Once connected, you can ask your assistant in plain language to send a document for signature, and it fills in the details and creates the case for you. Everything it creates shows up in your NextSign dashboard, exactly as if you had made it there.

MCP (Model Context Protocol) is the standard way AI assistants connect to outside tools. You don't need to know anything about it beyond one address and a login.

Beta. The server exposes four tools today — creating and sending signing cases, and browsing your document library to create cases from your own templates. More will follow, and details may change before general availability. The gaps are listed under Troubleshooting.

What you can ask for

  • "Send contract.pdf to jane@example.com for signature."
  • "Create a signing case for the Q3 agreement — Anna signs first, then Jonas."
  • "Send this to +45 12 34 56 78 by SMS for signing."
  • "Set it up as a draft so I can review it in NextSign before it goes out."
  • "Send our Employment Contract template to Andreas — he starts 1 September at 37 hours a week."
  • "Which templates do we have in NextSign, and what does the offer letter need filled in?"

The server address

https://api.nextsign.dk/v3/mcp

You paste this once, during setup — the Connect page walks through it. For the technically curious: it is a Streamable HTTP MCP server (stateless, no SSE), with OAuth sign-in or API-key authentication.

What you need

  • A NextSign account that is a member of a company.
  • An AI assistant that supports MCP connectors — Claude and ChatGPT both do.
  • Nothing else. Sign-in happens with your normal NextSign login during setup.

Where to start