Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect SignRequest to Claude Code

Let Claude prepare, send, and track signing requests in SignRequest. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect SignRequest to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect SignRequest, you add a SignRequest MCP server: a small hosted service that exposes SignRequest'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 SignRequest account. No API keys pasted into config files.

claude mcp add --transport http signrequest 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 SignRequest once connected?

Full read-write SignRequest access lets Claude create a signing request from a template or uploaded document, add signers and their order, send reminders, and dispatch the request once you approve. The preparation and follow-up that meant manual setup happen where your documents and audit trail already live.

  • Create a signing request from an existing template
  • Add signers and set their signing order before sending
  • Send a prepared signing request after you approve it
  • Send a reminder to a signer who has not yet completed
  • Look up the status of an open request and summarize what is outstanding
  • Cancel or withdraw a pending signing request when a deal changes

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 SignRequest 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 SignRequest API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SignRequest 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 SignRequest 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 SignRequest 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 SignRequest 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 SignRequest'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 SignRequest?
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 SignRequest account it signs in with. Revoking access is one click in SignRequest.

More on the SignRequest connector

SignRequest connector for claude.aiSignNow + 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