Skip to main content

Adobe Sign MegaSign MCP Server

Create a powerful Model Context Protocol (MCP) server for Adobe Sign MegaSign in minutes with our AI Gateway. This guide walks you through setting up bulk agreement distribution with enterprise-grade security and instant OAuth authentication.

About Adobe Sign MegaSign API​

Adobe Sign MegaSign enables sending personalized agreements to hundreds or thousands of recipients simultaneously. The MegaSign API provides programmatic access to create, manage, and track bulk sending campaigns with individual customization for each recipient.

Key Capabilities​

  • Bulk Distribution: Send to unlimited recipients
  • Personalization: Unique agreements per recipient
  • Data Merge: Dynamic field population
  • Campaign Management: Track bulk sends
  • Individual Tracking: Per-recipient status
  • Reminder Automation: Bulk reminders
  • CSV Integration: Data import/export
  • Analytics: Campaign performance

API Features​

  • REST API v6: MegaSign operations
  • Batch Processing: Efficient bulk handling
  • OAuth 2.0: Secure authentication
  • Status Tracking: Real-time updates
  • Error Handling: Failed send management
  • Template Support: Reusable documents
  • Scheduling: Timed distributions
  • Reporting: Comprehensive analytics

What You Can Do with Adobe Sign MegaSign MCP Server​

The MCP server transforms Adobe Sign MegaSign API into a natural language interface, enabling AI agents to:

Bulk Campaign Creation​

  • Campaign Setup

    • "Create MegaSign for 1000 employees"
    • "Set up bulk NDA distribution"
    • "Launch customer agreement campaign"
    • "Send personalized contracts"

  • Recipient Management

    • "Import recipients from CSV"
    • "Add 500 email addresses"
    • "Include custom fields per recipient"
    • "Set unique deadlines"

  • Template Configuration

    • "Use employment contract template"
    • "Apply sales agreement form"
    • "Configure document settings"
    • "Set signature requirements"

Personalization​

  • Field Mapping

    • "Map employee names to fields"
    • "Insert unique contract values"
    • "Add personalized messages"
    • "Configure dynamic content"

  • Custom Data

    • "Import salary information"
    • "Add department codes"
    • "Include start dates"
    • "Set individual terms"

  • Conditional Content

    • "Show sections by role"
    • "Include region-specific terms"
    • "Add language variants"
    • "Configure custom clauses"

Campaign Management​

  • Launch Control

    • "Send immediately"
    • "Schedule for Monday 9am"
    • "Stagger sending over days"
    • "Test with subset first"

  • Progress Monitoring

    • "Show campaign status"
    • "Track completion rate"
    • "Monitor bounce rate"
    • "Check delivery status"

  • Reminder Management

    • "Send bulk reminders"
    • "Target non-signers only"
    • "Customize reminder message"
    • "Set reminder schedule"

Analytics & Reporting​

  • Campaign Metrics

    • "Show overall completion rate"
    • "Calculate average time to sign"
    • "Track daily progress"
    • "Measure engagement rate"

  • Recipient Analytics

    • "List completed signers"
    • "Show pending recipients"
    • "Identify bottlenecks"
    • "Export status report"

  • Performance Insights

    • "Compare campaign performance"
    • "Analyze by recipient group"
    • "Track by geography"
    • "Monitor device usage"

Error Handling​

  • Failed Sends

    • "Show failed deliveries"
    • "Retry failed sends"
    • "Update incorrect emails"
    • "Handle bounced addresses"

  • Validation Errors

    • "Check data format issues"
    • "Identify missing fields"
    • "Validate email addresses"
    • "Fix merge conflicts"

  • Recovery Actions

    • "Resend to failed recipients"
    • "Update recipient data"
    • "Replace invalid emails"
    • "Continue partial sends"

Data Management​

  • CSV Operations

    • "Import recipient list"
    • "Map CSV columns to fields"
    • "Export campaign data"
    • "Update bulk data"

  • Field Mapping

    • "Configure column mappings"
    • "Set data transformations"
    • "Handle special characters"
    • "Validate data types"

  • Data Validation

    • "Check email formats"
    • "Verify required fields"
    • "Validate custom data"
    • "Preview merged documents"

Enterprise Features​

  • Compliance Controls

    • "Enable audit trails"
    • "Track all actions"
    • "Maintain records"
    • "Export compliance data"

  • Security Settings

    • "Require authentication"
    • "Set access controls"
    • "Enable encryption"
    • "Configure retention"

  • Integration Options

    • "Connect to HR system"
    • "Sync with CRM"
    • "Update databases"
    • "Trigger workflows"

Advanced Configuration​

  • Sending Options

    • "Set sending limits"
    • "Configure rate limiting"
    • "Enable test mode"
    • "Set priority levels"

  • Response Handling

    • "Route signed documents"
    • "Trigger completions"
    • "Update systems"
    • "Send notifications"

  • Workflow Integration

    • "Chain with workflows"
    • "Trigger follow-ups"
    • "Create tasks"
    • "Update records"

Prerequisites​

  • Access to Cequence AI Gateway
  • Adobe Sign Enterprise plan with MegaSign
  • MegaSign permissions enabled
  • OAuth application credentials

Step 1: Create Adobe Sign Integration​

1.1 Access Adobe Sign Admin​

  1. Log in to Adobe Sign as administrator
  2. Go to Account MegaSign
  3. Navigate to API Applications
  4. Select Create Application

1.2 Configure OAuth Application​

  1. Fill in application details:
    • Application Name: "AI Gateway MegaSign MCP"
    • Application Display Name: "Bulk Send Manager"
    • Redirect URI: 
      https://auth.aigateway.cequence.ai/v1/outbound/oauth/callback

1.3 Set Application Scopes​

Select required scopes:

  • agreement_send - Send agreements
  • agreement_write - Create agreements
  • agreement_read - View status
  • megasign_read - View MegaSigns
  • megasign_write - Create MegaSigns
  • library_read - Access templates
  • user_read - User information

1.4 Get Credentials​

  1. After creation, view application
  2. Copy Client ID
  3. Copy Client Secret
  4. Note the Base URI for your region

Step 2-4: Standard Setup​

Follow standard steps to access AI Gateway, find Adobe Sign MegaSign API, and create MCP server.

Step 5: Configure API Endpoints​

  1. Base URL: Your regional API endpoint
    • Example: https://api.na1.adobesign.com/api/rest/v6
  2. Select MegaSign endpoints:
    • MegaSign endpoints
    • Bulk operations endpoints
    • Status endpoints
  3. Click Next

Step 6: MCP Server Configuration​

  1. Name: "Adobe Sign MegaSign"
  2. Description: "Bulk agreement distribution"
  3. Configure production mode
  4. Click Next

Step 7: Configure Authentication​

  1. Authentication Type: OAuth 2.0
  2. Authorization URL: 
    https://secure.{region}.adobesign.com/public/oauth/v2
  3. Token URL: 
    https://api.{region}.adobesign.com/oauth/v2/token
  4. Enter Client ID and Secret
  5. Select required scopes

Available Adobe Sign MegaSign OAuth Scopes​

MegaSign Operations​

  • megasign_read:self

    • View own MegaSigns
    • Check campaign status
    • Access recipient list
    • View analytics

  • megasign_write:self

    • Create MegaSigns
    • Send bulk agreements
    • Manage campaigns
    • Update settings

Extended Permissions​

  • megasign_read:group

    • View group MegaSigns
    • Monitor team campaigns
    • Access shared bulk sends

  • megasign_write:group

    • Manage group MegaSigns
    • Create team campaigns
    • Update shared sends

  • megasign_read:account

    • Full MegaSign visibility
    • Administrative access
    • Compliance monitoring

For MegaSign Users:

megasign_read:self
megasign_write:self
agreement_send:self
agreement_read:self
library_read:self

For MegaSign Administrators:

megasign_read:account
megasign_write:account
agreement_read:account
agreement_write:account
library_read:account
user_read:account

Step 8-10: Complete Setup​

Configure security, choose deployment, and deploy.

Using Your Adobe Sign MegaSign MCP Server​

With Claude Desktop​

{
  "servers": {
    "adobe-sign-megasign": {
      "url": "your-mcp-server-url",
      "auth": {
        "type": "oauth2",
        "client_id": "your-client-id"
      }
    }
  }
}

Natural Language Commands​

  • "Send employment contracts to 500 new hires"
  • "Create bulk NDA campaign from CSV file"
  • "Show MegaSign completion status"
  • "Send reminders to unsigned recipients"
  • "Export campaign results to spreadsheet"

API Integration Example​

// Initialize MCP client
const mcpClient = new MCPClient({
  serverUrl: 'your-mcp-server-url',
  auth: {
    type: 'oauth2',
    token: 'access-token'
  }
});

// Create MegaSign campaign
const megaSign = await mcpClient.adobeSign.megaSign.create({
  name: 'Annual Policy Acknowledgment',
  signatureType: 'ESIGN',
  state: 'IN_PROCESS',
  message: 'Please review and acknowledge the updated company policies.',
  fileInfos: [{
    libraryDocumentId: 'policy-template-2025'
  }],
  signatureFlow: 'SENDER_SIGNATURE_NOT_REQUIRED'
});

// Import recipients from CSV
const recipients = await mcpClient.adobeSign.megaSign.importCSV({
  megaSignId: megaSign.id,
  csvFile: {
    name: 'employees.csv',
    content: `email,firstName,lastName,department,employeeId
john.doe@company.com,John,Doe,Engineering,EMP001
jane.smith@company.com,Jane,Smith,Marketing,EMP002
robert.jones@company.com,Robert,Jones,Sales,EMP003`
  },
  fieldMappings: [
    { csvColumn: 'email', megaSignField: 'recipientEmail' },
    { csvColumn: 'firstName', megaSignField: 'firstName' },
    { csvColumn: 'lastName', megaSignField: 'lastName' },
    { csvColumn: 'department', megaSignField: 'department' },
    { csvColumn: 'employeeId', megaSignField: 'employeeNumber' }
  ]
});

// Add recipients programmatically
const bulkRecipients = await mcpClient.adobeSign.megaSign.addRecipients({
  megaSignId: megaSign.id,
  recipients: [
    {
      email: 'alice.brown@company.com',
      firstName: 'Alice',
      lastName: 'Brown',
      customFields: {
        department: 'HR',
        employeeId: 'EMP004',
        startDate: '2025-01-15',
        manager: 'Sarah Johnson'
      }
    },
    {
      email: 'bob.wilson@company.com',
      firstName: 'Bob',
      lastName: 'Wilson',
      customFields: {
        department: 'Finance',
        employeeId: 'EMP005',
        startDate: '2025-02-01',
        manager: 'Mike Davis'
      }
    }
  ]
});

// Configure campaign settings
await mcpClient.adobeSign.megaSign.updateSettings({
  megaSignId: megaSign.id,
  settings: {
    reminderFrequency: 'DAILY_UNTIL_SIGNED',
    firstReminderDelay: 3,
    completionDeadline: 30,
    locale: 'en_US',
    authenticationMethod: 'EMAIL',
    externalId: 'POLICY-2025-Q1',
    postSignOptions: {
      redirectUrl: 'https://company.com/policies/acknowledged',
      redirectDelay: 5
    }
  }
});

// Send MegaSign campaign
const sendResult = await mcpClient.adobeSign.megaSign.send({
  megaSignId: megaSign.id,
  sendOptions: {
    scheduledTime: '2025-02-01T09:00:00Z',
    sendInBatches: true,
    batchSize: 100,
    batchDelay: 60, // seconds between batches
    testMode: false,
    validateOnly: false
  }
});

// Monitor campaign progress
const status = await mcpClient.adobeSign.megaSign.getStatus({
  megaSignId: megaSign.id,
  includeDetails: true
});

console.log(`Total recipients: ${status.totalRecipients}`);
console.log(`Sent: ${status.sentCount}`);
console.log(`Completed: ${status.completedCount}`);
console.log(`Failed: ${status.failedCount}`);

// Get detailed recipient status
const recipientStatus = await mcpClient.adobeSign.megaSign.getRecipientStatus({
  megaSignId: megaSign.id,
  pageSize: 100,
  status: 'WAITING_FOR_MY_SIGNATURE'
});

// Send targeted reminders
await mcpClient.adobeSign.megaSign.sendReminders({
  megaSignId: megaSign.id,
  reminderOptions: {
    targetStatus: ['WAITING_FOR_MY_SIGNATURE', 'VIEWED'],
    customMessage: 'This is a friendly reminder to complete your policy acknowledgment.',
    includeDocument: true
  }
});

// Handle failed sends
const failures = await mcpClient.adobeSign.megaSign.getFailures({
  megaSignId: megaSign.id
});

for (const failure of failures.items) {
  if (failure.reason === 'INVALID_EMAIL') {
    // Update email and retry
    await mcpClient.adobeSign.megaSign.updateRecipient({
      megaSignId: megaSign.id,
      recipientId: failure.recipientId,
      updates: {
        email: failure.suggestedEmail || 'hr@company.com'
      }
    });
  }
}

// Retry failed sends
await mcpClient.adobeSign.megaSign.retryFailed({
  megaSignId: megaSign.id,
  recipientIds: failures.items.map(f => f.recipientId)
});

// Export campaign results
const exportData = await mcpClient.adobeSign.megaSign.exportResults({
  megaSignId: megaSign.id,
  format: 'CSV',
  includeFields: [
    'recipientEmail',
    'status',
    'signedDate',
    'ipAddress',
    'customFields'
  ]
});

// Create follow-up MegaSign for non-signers
const nonSigners = recipientStatus.items.filter(
  r => r.status === 'WAITING_FOR_MY_SIGNATURE'
);

if (nonSigners.length > 0) {
  const followUpMegaSign = await mcpClient.adobeSign.megaSign.create({
    name: 'Policy Acknowledgment - Final Notice',
    basedOn: megaSign.id,
    recipients: nonSigners.map(r => ({
      email: r.email,
      customFields: r.customFields
    })),
    message: 'URGENT: Please acknowledge company policies within 48 hours.'
  });
}

// Get analytics
const analytics = await mcpClient.adobeSign.megaSign.getAnalytics({
  megaSignId: megaSign.id,
  metrics: [
    'completionRate',
    'averageTimeToSign',
    'deviceBreakdown',
    'geographicDistribution',
    'hourlyActivity'
  ]
});

// Archive completed campaign
await mcpClient.adobeSign.megaSign.archive({
  megaSignId: megaSign.id,
  archiveOptions: {
    includeDocuments: true,
    includeAuditTrails: true,
    retentionPeriod: 7 // years
  }
});

Common Use Cases​

HR Campaigns​

  • Policy acknowledgments
  • Benefits enrollment
  • Training confirmations
  • Compliance forms

Sales Operations​

  • Contract renewals
  • Price updates
  • Terms acceptance
  • Quote approvals

Customer Communications​

  • Service agreements
  • Privacy updates
  • Terms of service
  • Consent forms

Vendor Management​

  • Supplier agreements
  • Code of conduct
  • Certification updates
  • Compliance attestations

Security Best Practices​

  1. Data Security:

    • Encrypt CSV files
    • Secure data transmission
    • Validate recipient data
    • Audit bulk operations

  2. Campaign Control:

    • Test before sending
    • Use staged rollouts
    • Monitor progress
    • Handle errors promptly

  3. Compliance:

    • Maintain audit trails
    • Track consent
    • Archive campaigns
    • Document processes

Troubleshooting​

Common Issues​

  1. Send Failures

    • Verify email formats
    • Check template access
    • Validate merge fields
    • Review rate limits

  2. Data Import Errors

    • Check CSV formatting
    • Verify column mappings
    • Validate required fields
    • Handle special characters

  3. Performance Issues

    • Use batch sending
    • Optimize recipient lists
    • Monitor API limits
    • Implement retries

Getting Help​