Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect SignNow to Claude Code

Let Claude prepare documents and send them for signature in SignNow. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect SignNow to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect SignNow, you add a SignNow MCP server: a small hosted service that exposes SignNow's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own SignNow account. No API keys pasted into config files.

claude mcp add --transport http signnow https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in SignNow once connected?

Full read-write SignNow access lets Claude upload a document, place signer and field tags, set the signing order, send a document or invite for signature, and check completion status. The signature prep that used to mean clicking through the SignNow editor happens where your request already lives.

  • Upload a document and add signer, date, and text fields
  • Create a signing order across multiple recipients
  • Send a document or signing invite once you approve it
  • Generate a reusable template from an existing document
  • Check the status of documents out for signature and flag stalled ones
  • Download a completed document with its audit trail

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same SignNow access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the SignNow API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SignNow changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build SignNow connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same SignNow connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own SignNow account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on SignNow's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to SignNow?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the SignNow account it signs in with. Revoking access is one click in SignNow.

More on the SignNow connector

SignNow connector for claude.aiSignRequest + Claude CodeProposify + Claude CodeQwilr + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us