Sproof MCP. Manage Signatures & Compliance Workflows.

You're connecting Sproof to your AI agent so you can handle digital signatures that meet European compliance standards—eIDAS. This whole server manages documents, keeps track of who signs what, and handles contact records; you do it all through natural language chat.

To get started, you don't need to jump between web portals. You just tell your agent what you need done. If you want a full roster of every file Sproof is tracking for compliance, use list_documents. Need the nitty-gritty details on one specific document? Run get_document to pull its metadata and current status.

When it comes time to get documents signed, your agent takes over the whole workflow. You can kick off a new signing process using create_signature_request, starting the chain for a document that needs multiple approvals. Want to see what requests are currently active or waiting for someone to sign? Just ask for a summary of all outstanding requests with list_signature_requests.

If you realize a signature request is stalled and it shouldn't be, you can use cancel_signature_request to stop the process before it goes further.

To control the flow, your agent lets you define the signers. You retrieve the names of people who need to sign using list_signers, which shows exactly who needs to approve the document and in what order. It handles sequencing so you can make sure approvals come in the right way.

If you find a specific request is confusing, you pull up all its details with get_signature_request.

Before anyone can sign, your agent helps you manage contacts. You get a complete list of every person or company stored in the system with list_contacts. Need to add someone new who's going to be signing? Use create_contact to build out that new record right from the chat. This keeps all your signer information current.

For legal and compliance teams, this is where the server shines. When you need proof of validity, you run list_audit_trail. That gives you a step-by-step timeline of every action taken on a request, which is critical for proving document integrity. You also get your overall system context by calling get_profile, pulling general account data and usage metrics.

If you're dealing with complex workflows, the agent makes sure everything connects: it starts the signing process (create_signature_request), manages who signs it in sequence (list_signers), lets you stop things if they go sideways (cancel_signature_request), and then gives you all the historical proof of every single step with list_audit_trail. You can check the status of any document using get_document, review a deep dive on one request using get_signature_request, or simply pull up the whole roster of managed files with list_documents.

Your agent handles all this communication, pulling fresh data from your Sproof account so you never have to switch screens. You're managing compliance-grade document signing and contact records—all in one conversation.