Ugosign MCP. Manage document signatures without leaving your agent.

Ugosign connects your AI agent directly to advanced electronic signature workflows. You use this server to programmatically create, track, and manage legally compliant document signing requests without ever touching a web dashboard.

Need to start a new agreement? You can run create_signature_request to send all the necessary data required for an electronic signature request, defining both the documents and the specific recipients who need to act on them.

To keep tabs on what’s happening across your organization, you've got two ways to list agreements. Run list_signature_requests to pull a summary of multiple active requests; this shows you exactly who needs to sign and gives you a quick read on the current status for every pending agreement. If you just want to see every document Ugosign is managing, use list_documents.

When you need deep status checks, you don't wanna rely on summaries. You can run get_signature_request with a specific ID to get the precise, current details and status for one single signing request. This tells you immediately if it’s pending, fully executed, or where else along the line it is stuck.

For document specifics, you've got get_document. Running this tool lets you pull all the granular metadata and specific details tied to a single document ID; that includes its entire version history and any associated data points.

Want an overview of your whole account? You can use get_organization to retrieve high-level information about your Ugosign account, checking things like user counts or if you're running low on signing capacity.

When all these tools work together with your agent, the process is clean. Your AI client handles the logic—you just tell it what data point you need. It executes the tool call and spits out structured JSON that your agent can use instantly to make decisions or update records. You're automating compliance; you aren't reading dashboards.

You can start by creating a workflow using create_signature_request. Then, if you need to know what happened with that agreement later, you run get_signature_request against the new ID. If you suddenly gotta check every document in the system—the ones drafted and the finalized ones—you call list_documents. You can also pull a summary of all active agreements at once using list_signature_requests, which tells you who needs to sign what right now.

It's all about precision. If you need full proof on a document, run get_document for its complete metadata and version history. And don’t forget your account health; check your limits with get_organization so you never get caught off guard by hitting capacity.