PRO Annual — 50 users, $106.80/year
Managing legal agreements and NDAs shouldn't involve jumping between portals. When Claude uses the Adobe Acrobat Sign MCP inside GitScrum, you delegate complex compliance tasks—like tracking signatory status or retrieving audit trails—turning a manual headache into a simple conversation on your board.
Claude
ChatGPT
Cursor
Gemini
Windsurf
VS Code
JetBrains
VercelConnected via Vinkius catalog · No credit card
task.delegate()
You write a specific task for Claude, asking it to initiate the signing process for a vendor contract or check the status of a critical NDA.
Claude autonomously executes the necessary functions via this MCP. It can list agreements, send reminders to slow signers, or retrieve the full legal audit trail without your input.
The result—a status update, a list of required participants, or the completed contract summary—is posted directly into the task comments, keeping your project visibility high.
task.create()
Copy. Paste into a Claude-aware GitScrum task. Done.
We just finalized a vendor relationship and need to get the signed Non-Disclosure Agreement out immediately.
Claude, please initiate the signing process. Use the Adobe Acrobat Sign MCP to create a new agreement using the attached template document and send it simultaneously to John Smith (signer) and Jane Doe (approver).
The project is blocked because we don't know if the client has signed the final scope of work agreement.
Claude, I need an update on our 'Project Nova Scope' agreement. Use the Adobe Acrobat Sign MCP to list all participants and tell me who still needs to sign it or if any reminders are needed.
We need to prove exactly when, how, and by whom the final legal document was signed for our compliance records.
Claude, pull the complete, legally binding audit trail using the Adobe Acrobat Sign MCP for agreement ID 789. I need confirmation of every action taken, including IP addresses and timestamps.
Before this, tracking down where a contract stood was pure administrative overhead. You'd spend hours jumping between email threads, internal dashboards, and separate legal portals just to confirm if the NDA had been signed or who needed to approve it next. It’s tedious, error-prone work that slows down project kickoffs.
Now, Claude reads the source directly via this MCP. Instead of manual status checks, you ask a question in GitScrum: 'Has the vendor contract closed?' Claude uses Adobe Acrobat Sign to pull the definitive answer—the real-time signing status or the full audit trail—and posts it back where you need it.
Open this workflow in GitScrum →Onboarding new hires or vendors used to mean a chaotic pile of documents, each requiring manual tracking. Did they sign the policy acknowledgment? Was the offer letter approved by HR yet? Missing one document meant delaying the entire project start date.
With Claude managing this MCP, you treat compliance like a ticket item. You ask for all pending agreements using Adobe Acrobat Sign, and Claude automatically compiles the list of outstanding participants and documents directly into your GitScrum backlog, ensuring zero risk.
claude.ask()
Claude, can you review our project documentation and use the Adobe Acrobat Sign MCP to list all agreements that are currently due for signature or have expired?
I just received a folder of final signed contracts. Claude, please check them using the Adobe Acrobat Sign MCP and summarize which ones were signed by an Approver versus just a basic Signer.
Before we close out this project phase, Claude needs to verify compliance. Use the Adobe Acrobat Sign MCP to search all agreements for any documents that lack a complete signatory list or are still in 'Draft' status.
Claude, find the most recent agreement related to the 'Marketing Campaign Q3'. Use the Adobe Acrobat Sign MCP and provide me with its current signing status.
tools.list()
Each tool is one operation Claude runs on your behalf.
| tool_name | operation |
|---|---|
| adobe_agreement_members | Claude can use this tool to list all participants (signers, approvers, CC recipients) for a specific agreement, showing their role and current signing status. |
| adobe_audit_trail | This function retrieves the legally binding audit trail for an Adobe Sign agreement. Claude uses it to generate a tamper-proof record of every action taken on the contract. |
| adobe_cancel_agreement | Claude executes this when a deal falls apart, canceling an active Adobe Sign agreement and notifying all parties automatically. |
| adobe_create_agreement | This is the primary workflow: Claude uses it to create a brand new e-signature agreement for contracts or NDAs that need immediate attention. |
| adobe_get_agreement | Use this tool when you have an ID. Claude gets complete details of a specific agreement, including all participants and metadata, providing full context in GitScrum. |
| adobe_list_agreements | Claude calls this to list all agreements associated with your project, detailing their name, current status (e.g., SIGNED, OUT_FOR_SIGNATURE), and creation date. |
| adobe_list_library_documents | This function lets Claude browse reusable templates within Adobe Sign, listing available document types that can be referenced for new agreement creation. |
| adobe_search_agreements | Claude uses this to find specific agreements across your entire signature pipeline by searching using a name or keyword in GitScrum. |
| adobe_send_reminder | When prompted, Claude sends a reminder email to all pending signers on an active Adobe Sign agreement, gently nudging them toward completion. |
| adobe_upload_document | Returns a transientDocumentId that is then used in adobe_create_agreement fileInfos. This is the standard workflow: (1) upload document → (2) create agreement with the transientDocumentId → (3) agreement is sent for signature. Upload a document to Adobe Sign as a transient document — the first step before creating an agreement for signature |
grade
F
tools
10
auth
Required
catalog
Vinkius
faq.read()
Free for small teams. Set up in 5 minutes. Cancel anytime.
GitScrum lists this MCP as a Vinkius partner. Installations happen on Vinkius.
Connect GitScrum with the tools your team already uses. Native integrations with Git providers and communication platforms.
GitHub
GitLab
Bitbucket
Slack
Teams
Discord
Zapier
PabblyConnect with 3,000+ apps via Zapier & Pabbly
