2,500+ MCP servers ready to use
Vinkius

Adobe Acrobat Sign MCP Server for Mastra AI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Adobe Acrobat Sign through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "adobe-acrobat-sign": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Adobe Acrobat Sign Agent",
    instructions:
      "You help users interact with Adobe Acrobat Sign " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Adobe Acrobat Sign?"
  );
  console.log(result.text);
}

main();
Adobe Acrobat Sign
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Adobe Acrobat Sign MCP Server

Connect your Adobe Acrobat Sign account to any AI agent and manage your entire e-signature workflow through natural conversation.

Mastra's agent abstraction provides a clean separation between LLM logic and Adobe Acrobat Sign tool infrastructure. Connect 10 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

What you can do

  • Agreements — List, search, create, and cancel e-signature agreements
  • Signing Status — Track who has signed, who is pending, and send reminders to signers
  • Audit Trails — Access legally binding audit trails for any signed agreement
  • Library Documents — Browse reusable templates and library documents
  • Document Upload — Upload documents for signature via the transient document workflow
  • Participants — View all signers, approvers, and CC recipients with their status

The Adobe Acrobat Sign MCP Server exposes 10 tools through the Vinkius. Connect it to Mastra AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Adobe Acrobat Sign to Mastra AI via MCP

Follow these steps to integrate the Adobe Acrobat Sign MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 10 tools from Adobe Acrobat Sign via MCP

Why Use Mastra AI with the Adobe Acrobat Sign MCP Server

Mastra AI provides unique advantages when paired with Adobe Acrobat Sign through the Model Context Protocol.

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Adobe Acrobat Sign without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Adobe Acrobat Sign tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

Adobe Acrobat Sign + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Adobe Acrobat Sign MCP Server delivers measurable value.

01

Automated workflows: build multi-step agents that query Adobe Acrobat Sign, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Adobe Acrobat Sign as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Adobe Acrobat Sign on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Adobe Acrobat Sign tools alongside other MCP servers

Adobe Acrobat Sign MCP Tools for Mastra AI (10)

These 10 tools become available when you connect Adobe Acrobat Sign to Mastra AI via MCP:

01

adobe_agreement_members

Returns each member email, role (SIGNER/APPROVER/ACCEPTOR/FORM_FILLER/DELEGATE_TO_SIGNER/CC), and their signing status. Use to check who has signed, who is pending, or to review the signing workflow. Get all participants (signers, approvers, CC recipients) in a specific Adobe Sign agreement with their roles and status

02

adobe_audit_trail

The audit trail is a legally binding record of all actions taken: when the agreement was created, viewed, signed, and by whom (with IP addresses and timestamps). Essential for legal compliance and dispute resolution. Get the legal audit trail for an Adobe Sign agreement — a tamper-proof record of all signing events and actions

03

adobe_cancel_agreement

This is irreversible — the agreement cannot be re-sent (a new one must be created). An optional comment explains the cancellation reason to all participants. Use when a deal falls through, terms change, or the document needs to be replaced. Cancel an Adobe Sign agreement that is currently out for signature — stops the signing process and notifies all parties

04

adobe_create_agreement

Create a new Adobe Sign agreement and send it for signature — the core e-signature workflow for contracts, NDAs, and legal documents

05

adobe_get_agreement

Returns name, status, all participant sets with their roles (SIGNER/APPROVER/CC/DELEGATE), signature type, creation and modification dates, and any external IDs. Use after listing agreements to drill into a specific agreement for complete information. Get complete details of a specific Adobe Sign agreement by ID, including all participants, signing status, and document metadata

06

adobe_list_agreements

Returns agreement name, current status, signature type (ESIGN/WRITTEN), creator email, and creation/modification dates. Agreement statuses: DRAFT (being built), OUT_FOR_SIGNATURE (awaiting signatures), SIGNED (fully executed), CANCELLED, EXPIRED. Use when the user asks about pending signatures, completed agreements, or document pipeline. List Adobe Acrobat Sign agreements with name, status (DRAFT/OUT_FOR_SIGNATURE/SIGNED/CANCELLED/EXPIRED), sender, and dates

07

adobe_list_library_documents

Library documents are reusable templates that can be referenced when creating new agreements. Returns document name, ID (for use in adobe_create_agreement fileInfos), sharing mode, and creation date. Use when the user asks "what templates do we have?" or needs a library document ID. List reusable library documents (templates) in Adobe Sign — pre-built agreements, forms, and document templates

08

adobe_search_agreements

Returns matching agreements with names, statuses, and dates. Use when the user wants to find a specific agreement, look up a contract by name, or search across the document library. Search Adobe Sign agreements by name or keyword to find specific documents across your signature pipeline

09

adobe_send_reminder

The agreement must be in OUT_FOR_SIGNATURE status. An optional comment is included in the reminder email. Use when the user says "remind them to sign" or "send a reminder for the contract." Send a signing reminder to all pending signers on an Adobe Sign agreement — nudges recipients who have not yet signed

10

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

Example Prompts for Adobe Acrobat Sign in Mastra AI

Ready-to-use prompts you can give your Mastra AI agent to start working with Adobe Acrobat Sign immediately.

01

"Show me all agreements waiting for signature"

Troubleshooting Adobe Acrobat Sign MCP Server with Mastra AI

Common issues when connecting Adobe Acrobat Sign to Mastra AI through the Vinkius, and how to resolve them.

01

createMCPClient not exported

Install: npm install @mastra/mcp

Adobe Acrobat Sign + Mastra AI FAQ

Common questions about integrating Adobe Acrobat Sign MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Adobe Acrobat Sign to Mastra AI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.