Adobe Sign Library MCP Server

Create a powerful Model Context Protocol (MCP) server for Adobe Sign Library in minutes with our AI Gateway. This guide walks you through setting up seamless document template management with enterprise-grade security and instant OAuth authentication.

About Adobe Sign Library API

The Adobe Sign Library API provides comprehensive access to document templates, reusable forms, and shared resources. It enables organizations to create, manage, and distribute standardized documents for consistent signing experiences across teams and workflows.

Key Capabilities

• Template Management: Create and organize templates
• Document Library: Centralized document storage
• Form Fields: Reusable field configurations
• Version Control: Template versioning
• Sharing Controls: Team collaboration
• Custom Branding: Template customization
• Field Mapping: Data integration
• Access Management: Permission controls

API Features

• REST API v6: Library operations
• Template Builder: Programmatic creation
• OAuth 2.0: Secure authentication
• Bulk Operations: Mass template management
• Field Library: Reusable components
• Template Analytics: Usage tracking
• Import/Export: Template migration
• Metadata Management: Custom properties

What You Can Do with Adobe Sign Library MCP Server

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

Template Creation

• Document Templates

  • "Create sales contract template"
  • "Build NDA template"
  • "Design employment agreement"
  • "Set up purchase order template"

• Template Configuration

  • "Add signature fields"
  • "Configure form fields"
  • "Set field properties"
  • "Define signing order"

• Field Libraries

  • "Create reusable field set"
  • "Build standard form fields"
  • "Design custom field types"
  • "Configure validation rules"

Library Organization

• Folder Management

  • "Create template categories"
  • "Organize by department"
  • "Build folder hierarchy"
  • "Set folder permissions"

• Template Collections

  • "Group related templates"
  • "Create template bundles"
  • "Build workflow sets"
  • "Manage template suites"

• Search & Discovery

  • "Find templates by name"
  • "Search by field type"
  • "Filter by department"
  • "Browse by category"

Template Customization

• Branding Options

  • "Apply company branding"
  • "Set template colors"
  • "Add logo placement"
  • "Configure fonts"

• Layout Design

  • "Create multi-page templates"
  • "Design responsive layouts"
  • "Add headers and footers"
  • "Configure page settings"

• Dynamic Content

  • "Add merge fields"
  • "Create conditional sections"
  • "Build calculation fields"
  • "Set default values"

Access Control

• Sharing Settings

  • "Share with team"
  • "Set view permissions"
  • "Grant edit rights"
  • "Control distribution"

• Permission Levels

  • "Set template ownership"
  • "Configure admin access"
  • "Manage user permissions"
  • "Create access groups"

• Usage Restrictions

  • "Limit template usage"
  • "Set expiration dates"
  • "Configure quotas"
  • "Track utilization"

Version Management

• Version Control

  • "Create template version"
  • "Track version history"
  • "Compare versions"
  • "Restore previous version"

• Change Tracking

  • "Log template changes"
  • "Track field modifications"
  • "Monitor access history"
  • "Audit template usage"

• Publishing Workflow

  • "Create draft version"
  • "Submit for approval"
  • "Publish template"
  • "Archive old versions"

Field Management

• Field Types

  • "Add text input fields"
  • "Create signature blocks"
  • "Insert date fields"
  • "Build dropdown menus"

• Field Properties

  • "Set required fields"
  • "Configure validation"
  • "Add help text"
  • "Define field rules"

• Field Libraries

  • "Create field groups"
  • "Build reusable sets"
  • "Share field configs"
  • "Import field templates"

Template Analytics

• Usage Metrics

  • "Track template usage"
  • "Monitor adoption rates"
  • "Analyze completion times"
  • "Measure success rates"

• Performance Reports

  • "Most used templates"
  • "User activity reports"
  • "Department usage"
  • "Template effectiveness"

• Optimization Insights

  • "Identify bottlenecks"
  • "Track field errors"
  • "Monitor drop-offs"
  • "Suggest improvements"

Import/Export

• Template Migration

  • "Import Word templates"
  • "Convert PDF forms"
  • "Export to formats"
  • "Bulk template import"

• Data Portability

  • "Export template library"
  • "Backup configurations"
  • "Transfer between accounts"
  • "Archive templates"

• Integration Support

  • "Sync with systems"
  • "API template access"
  • "Webhook notifications"
  • "External storage"

Prerequisites

• Access to Cequence AI Gateway
• Adobe Sign Business or Enterprise plan
• Library management permissions
• 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 Library
3. Navigate to API Applications
4. Select Create Application

1.2 Configure OAuth Application

1. Fill in application details:
   • Application Name: "AI Gateway Library MCP"
   • Application Display Name: "Template Manager"
   • Redirect URI:

     https://auth.aigateway.cequence.ai/v1/outbound/oauth/callback

1.3 Set Application Scopes

Select required scopes:

• library_read - View library documents
• library_write - Manage templates
• library_retention - Access versions
• agreement_read - Template usage
• agreement_write - Create from template
• user_read - User permissions

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 Library 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 Library endpoints:
   • Library documents endpoints
   • Templates endpoints
   • Fields endpoints
3. Click Next

Step 6: MCP Server Configuration

1. Name: "Adobe Sign Library"
2. Description: "Template and document management"
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 Library OAuth Scopes

Library Management

• library_read:self

  • View own templates
  • Access library documents
  • Read template details
  • View field configurations

• library_write:self

  • Create templates
  • Modify own templates
  • Upload documents
  • Configure fields

• library_retention:self

  • Access version history
  • Restore versions
  • Track changes
  • Archive templates

Extended Permissions

• library_read:group

  • View group templates
  • Access shared library
  • Read team templates

• library_write:group

  • Manage group templates
  • Create shared templates
  • Update team library

• library_read:account

  • Full library access
  • Administrative view
  • Compliance monitoring

Recommended Scope Combinations

For Template Users:

library_read:self
agreement_write:self
user_read:self

For Template Administrators:

library_read:account
library_write:account
library_retention:account
agreement_read:account
user_read:account

Step 8-10: Complete Setup

Configure security, choose deployment, and deploy.

Using Your Adobe Sign Library MCP Server

With Claude Desktop

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

Natural Language Commands

• "Create employment contract template"
• "Add signature fields to NDA template"
• "Share sales templates with team"
• "Show most used templates this month"
• "Update company branding on all templates"

API Integration Example

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

// Create a library template
const template = await mcpClient.adobeSign.library.create({
  name: 'Sales Contract Template',
  description: 'Standard sales agreement for products',
  sharingMode: 'GROUP',
  templateTypes: ['DOCUMENT'],
  fileInfos: [{
    transientDocumentId: 'uploaded-doc-id'
  }],
  state: 'ACTIVE'
});

// Configure template fields
const fields = await mcpClient.adobeSign.library.addFields({
  libraryDocumentId: template.id,
  fields: [
    {
      name: 'buyerName',
      type: 'TEXT',
      pageNumber: 1,
      rect: {
        x: 100,
        y: 200,
        width: 200,
        height: 30
      },
      displayLabel: 'Buyer Name',
      required: true,
      readOnly: false,
      validation: {
        type: 'STRING',
        pattern: '^[a-zA-Z\\s]+$'
      }
    },
    {
      name: 'contractValue',
      type: 'NUMBER',
      pageNumber: 1,
      rect: {
        x: 100,
        y: 250,
        width: 150,
        height: 30
      },
      displayLabel: 'Contract Value',
      required: true,
      format: 'CURRENCY',
      defaultValue: '0.00'
    },
    {
      name: 'effectiveDate',
      type: 'DATE',
      pageNumber: 1,
      rect: {
        x: 100,
        y: 300,
        width: 150,
        height: 30
      },
      displayLabel: 'Effective Date',
      required: true,
      format: 'MM/DD/YYYY'
    },
    {
      name: 'buyerSignature',
      type: 'SIGNATURE',
      pageNumber: 3,
      rect: {
        x: 100,
        y: 600,
        width: 200,
        height: 60
      },
      displayLabel: 'Buyer Signature',
      required: true,
      assignedTo: 'SIGNER1'
    }
  ]
});

// Create field library
const fieldLibrary = await mcpClient.adobeSign.library.createFieldSet({
  name: 'Standard Contract Fields',
  description: 'Reusable fields for contracts',
  fields: [
    {
      name: 'partyName',
      type: 'TEXT',
      displayLabel: 'Party Name',
      validation: { type: 'STRING' }
    },
    {
      name: 'partyAddress',
      type: 'TEXT',
      displayLabel: 'Address',
      multiline: true
    },
    {
      name: 'partySignature',
      type: 'SIGNATURE',
      displayLabel: 'Authorized Signature'
    },
    {
      name: 'signatureDate',
      type: 'DATE',
      displayLabel: 'Date',
      format: 'MM/DD/YYYY'
    }
  ]
});

// Apply branding to template
await mcpClient.adobeSign.library.updateBranding({
  libraryDocumentId: template.id,
  branding: {
    headerImage: 'https://company.com/logo.png',
    headerText: 'Confidential Sales Agreement',
    footerText: 'Page {page} of {total}',
    backgroundColor: '#f5f5f5',
    fontColor: '#333333',
    fontFamily: 'Helvetica, Arial, sans-serif'
  }
});

// Create template folder structure
const folder = await mcpClient.adobeSign.library.createFolder({
  name: 'Sales Templates',
  parentFolderId: 'root',
  description: 'Templates for sales team',
  permissions: {
    inherit: false,
    groups: [
      {
        groupId: 'sales-team-group',
        permission: 'EDIT'
      },
      {
        groupId: 'legal-team-group',
        permission: 'VIEW'
      }
    ]
  }
});

// Move template to folder
await mcpClient.adobeSign.library.moveToFolder({
  libraryDocumentId: template.id,
  folderId: folder.id
});

// Create template version
const newVersion = await mcpClient.adobeSign.library.createVersion({
  libraryDocumentId: template.id,
  fileInfos: [{
    transientDocumentId: 'updated-doc-id'
  }],
  versionInfo: {
    versionNumber: '2.0',
    comments: 'Updated terms and conditions',
    modifiedBy: 'legal-team'
  }
});

// Share template with specific users
await mcpClient.adobeSign.library.share({
  libraryDocumentId: template.id,
  sharingInfo: {
    users: [
      {
        email: 'sales-manager@company.com',
        permission: 'EDIT'
      },
      {
        email: 'sales-rep@company.com',
        permission: 'USE'
      }
    ],
    message: 'New sales contract template available',
    allowDownload: true,
    allowModification: false
  }
});

// Get template analytics
const analytics = await mcpClient.adobeSign.library.getAnalytics({
  libraryDocumentId: template.id,
  dateRange: {
    start: '2025-01-01',
    end: '2025-01-31'
  },
  metrics: [
    'usage_count',
    'unique_users',
    'completion_rate',
    'average_completion_time',
    'field_error_rate'
  ]
});

// Import templates from external source
const importResult = await mcpClient.adobeSign.library.bulkImport({
  source: 'WORD_DOCUMENTS',
  documents: [
    {
      url: 'https://storage.company.com/templates/nda.docx',
      name: 'Non-Disclosure Agreement',
      autoDetectFields: true
    },
    {
      url: 'https://storage.company.com/templates/msa.docx',
      name: 'Master Service Agreement',
      fieldMapping: {
        'Company Name': 'companyName',
        'Effective Date': 'effectiveDate',
        'Signature': 'authorizedSignature'
      }
    }
  ],
  targetFolder: folder.id
});

// Clone template with modifications
const clonedTemplate = await mcpClient.adobeSign.library.clone({
  sourceLibraryDocumentId: template.id,
  name: 'Sales Contract - Enterprise',
  modifications: {
    fields: [
      {
        name: 'enterpriseDiscount',
        type: 'NUMBER',
        displayLabel: 'Enterprise Discount %',
        defaultValue: '20'
      }
    ],
    sharingMode: 'GLOBAL'
  }
});

Common Use Cases

Contract Management

• Sales agreements
• Service contracts
• NDAs and legal documents
• Partnership agreements

HR Templates

• Employment contracts
• Onboarding documents
• Policy acknowledgments
• Performance reviews

Financial Documents

• Loan applications
• Investment agreements
• Purchase orders
• Invoices

Compliance Forms

• Regulatory filings
• Audit documents
• Certification forms
• Consent agreements

Security Best Practices

1. Template Security:

   • Control access permissions
   • Monitor template usage
   • Audit modifications
   • Encrypt sensitive data

2. Version Control:

   • Track all changes
   • Require approvals
   • Maintain history
   • Archive old versions

3. Access Management:

   • Role-based permissions
   • Group-level controls
   • Usage restrictions
   • Activity monitoring

Troubleshooting

Common Issues

1. Template Errors

   • Verify document format
   • Check field placement
   • Validate permissions
   • Review sharing settings

2. Field Configuration

   • Confirm field types
   • Check coordinates
   • Verify validation rules
   • Test default values

3. Access Issues

   • Review user permissions
   • Check group membership
   • Verify folder access
   • Confirm sharing settings

Getting Help

• Documentation: AI Gateway Docs
• Support: support@cequence.ai
• Adobe Sign API: helpx.adobe.com/sign/using/api.html

---