Skip to main content

Adobe Sign MegaSign MCP server

MegaSign is Adobe Sign's bulk sending feature that lets you send personalized agreements to hundreds or thousands of recipients at once. An AI agent with access to MegaSign can create bulk campaigns, import recipient lists, merge personalized data into each copy, track individual signing status, and manage large-scale distributions. This integration is useful for HR teams sending offer letters or policy updates, sales teams distributing contract renewals, or any department that needs to send similar but personalized documents to many recipients simultaneously.

Setting up an MCP server

This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the individual application pages.

Before you begin​

You'll need:

  • Access to AI Gateway with permission to create MCP servers
  • API credentials for the application you're connecting (see the relevant application page for what to collect)

Create an MCP server​

Find the API in the catalog​

  1. Sign in to AI Gateway and select MCP Servers from the left navigation.
  2. Select New MCP Server.
  3. Search for the application you want to connect, then select it from the catalog.

Configure the server​

  1. Enter a Name for your server — something descriptive that identifies both the application and its purpose (for example, "Zendesk Support — Prod").
  2. Enter a Description so your team knows what the server is for.
  3. Set the Timeout value. 30 seconds works for most APIs; increase to 60 seconds for APIs that return large payloads.
  4. Toggle Production mode on if this server will be used in a live workflow.
  5. Select Next.

Configure authentication​

Enter the authentication details for the application. This varies by service — see the Authentication section of the relevant application page for the specific credentials, OAuth URLs, and scopes to use.

Configure security​

  1. Set any Rate limits appropriate for your use case and the API's own limits.
  2. Enable Logging if you want AI Gateway to record requests and responses for auditing.
  3. Select Next.

Deploy​

Review the summary, then select Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.

Connect to an AI client​

Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:

Tips​

  • You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
  • If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
  • You can edit a server's name, description, timeout, and security settings after deployment without redeploying.

Authentication​

Adobe Sign uses OAuth 2.0 for secure authentication. You'll need an Adobe Sign Enterprise account with MegaSign enabled. Create an OAuth application in your Adobe Sign account and configure these endpoints:

  • Authorization URL: https://secure.{region}.adobesign.com/public/oauth/v2
  • Token URL: https://api.{region}.adobesign.com/oauth/v2/token

The scopes you'll need are agreement_send to send agreements, agreement_write to create agreements, agreement_read to view status, megasign_read to access MegaSigns, megasign_write to create and manage bulk sends, and library_read to use templates. Optional scopes include user_read for recipient information.

Available tools​

These tools let you create, launch, monitor, and manage bulk agreement campaigns with per-recipient customization and status tracking.

ToolDescription
Create MegaSignSet up a new bulk send campaign with template and recipient list
Get MegaSign detailsRetrieve campaign information including status and progress
List MegaSignsFetch a list of bulk campaigns with filtering options
Send MegaSignLaunch a bulk campaign to all recipients
Get MegaSign statusCheck overall completion rate and delivery progress
List recipientsRetrieve all recipients in a MegaSign campaign
Get recipient statusCheck signing status for a specific recipient
Send reminderSend a bulk reminder to non-signing recipients
Cancel MegaSignStop a bulk campaign and revoke unsigned documents
Export resultsDownload a report of signing status for all recipients

Tips​

Always validate your recipient list for correct email addresses and merge field data before sending to avoid failed deliveries and data mismatches.

Start with a small test batch (10–20 recipients) before launching a full bulk campaign to verify that personalization and routing are working correctly.

Stagger large MegaSigns over multiple days or hours to avoid overwhelming your recipients and to simplify support if issues arise.

Use CSV import to map recipient data to merge fields automatically — this reduces manual errors and makes it easy to reuse the same recipient list across multiple campaigns.

Monitor the MegaSign status dashboard regularly and send targeted reminders to non-signers after 3–5 days to improve completion rates without overwhelming recipients with multiple emails.