SignRequest MCP. Automate Document Signing Workflows by Conversation.

Look, you don't want to jump between tabs or copy UUIDs just to get a signature. This server connects your AI client directly into SignRequest, letting you run whole document workflows using plain language commands. It handles everything from building the initial paperwork to making sure your internal systems know the second someone signs off.

Managing Your Workspace and Users

Want to see what's going on? You can pull a list of every user account managed in your organization by calling list_users. Similarly, if you need an overview of organizational units, use list_teams to grab all the configured teams. To make sure everyone has the right access and structure, you can also run list_templates, which gives you a roster of every reusable document template you've saved in the system.

Building and Getting Documents

To start fresh, you can build a brand-new document using create_document. You just gotta feed it either an uploaded file URL or a specific template UUID, and tell it who needs to sign. If you need details on one of those saved templates before building, use get_template with its unique UUID.

To get the full scoop on any existing paperwork, run get_document, feeding it the document's UUID for all the deep details.

When a document is done and needs to be wiped, you can delete it permanently using delete_document and the UUID. If you just need a simple inventory of everything floating around your account, list_documents gives you that list right away.

Running the Signing Workflow

Got a document ready? You'll use create_signrequest to kick off the official signing process for an existing file. This starts tracking the entire thing until it’s done. To check up on where things stand, you can pull all info about one specific request using get_signrequest, which shows you who signed and how far along everyone is.

If you need to verify a single document's status or details after sending out the request, use get_document again.

Automating Notifications (Webhooks)

Here's where the automation kicks in. You don't want to manually check for signatures; you wanna be notified instantly. To set that up, call create_webhook, giving it a URL so SignRequest can ping your systems when something happens—like someone signing or declining.

Need to see what webhooks are already running? Use list_webhooks to pull the list of all registered endpoints and check their current status and destination URLs. If you're debugging, run list_webhooks to get that full picture.

The Bottom Line: What You Can Do

You can use get_template by UUID to grab template details; you'll also need it for the create_document call. To manage your setup completely, run list_users, list_teams, and then check out all available templates with list_templates. If you want a list of every document associated with your account, list_documents provides that overview.

This collection lets you initiate the entire lifecycle: you build the paperwork (create_document), send it out (create_signrequest), track its status using UUIDs (get_signrequest, get_document), and connect it all to your other systems with webhooks. It's a complete loop, man.