Full read-write Claude connector for SignRequest
Let Claude prepare, send, and track signing requests in SignRequest
Stop setting up signing requests by hand and chasing signers in another tab. Claude builds the request from a template, adds the signers in order, and sends or reminds inside SignRequest, with outbound sends waiting for your approval.
SignRequest is an electronic signature platform for sending documents out for signing and tracking them to completion. Teams want Claude to do more than check status: to prepare a document, add signers, and send the signing request itself.
What is a SignRequest MCP server?
A SignRequest MCP server is a small hosted service that exposes SignRequest's data and actions to Claude over the Model Context Protocol, so Claude can agreements and signatures inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can SignRequest's current connector do today?
Today, SignRequest has no official Claude or MCP connector we are aware of, so out of the box Claude cannot create or send signing requests in your account. A custom SignRequest connector built on its API adds those write actions behind scoped, human-in-the-loop controls, so Claude prepares and sends inside SignRequest rather than alongside it.
What does full read-write SignRequest access unlock?
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
Can Claude send a signing request in SignRequest?
Yes, Claude can send a signing request in SignRequest with a custom connector. It prepares the request from a template or uploaded document, attaches the signers, then sends only after you approve. Sending is a separate, gated write action, so nothing goes out to a signer until you confirm it.
Can Claude add signers and set the signing order in SignRequest?
Yes. Claude can add signers and set the signing order in SignRequest before anything sends. It creates the request from a template or document, attaches each signer, and arranges who signs first. You review the prepared request, and read and write tools stay separate so preparation never sends on its own.
Can Claude check the status of a request and remind signers in SignRequest?
Claude can check the status of an open request in SignRequest and summarize what is still outstanding, then send a reminder to a signer who has not finished. It can also cancel a pending request when a deal changes. The connector inherits your own permissions and never gets more access than your account.
How a SignRequest connector works
We build a small MCP server that authenticates to SignRequest with a scoped API token or OAuth, using the narrowest access the work needs. Read tools (look up requests, check status) and write tools (create, send, remind, cancel) are kept separate, and outbound or destructive actions like sending a request require your confirmation. Claude never has more access than your own SignRequest account, and the server can run behind a firewall with IP allowlisting when your setup calls for it.
Frequently asked questions
Can Claude send a SignRequest signing request, not just check status?
Can Claude add signers and set the signing order before sending?
Does the connector get more access than I have in SignRequest?
Related connectors
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.
