Skip to main content

Adobe Sign library MCP server

Adobe Sign's library feature lets you store reusable document templates and form configurations that your team can use repeatedly. An AI agent with access to Adobe Sign library can create and organize templates, add form fields, manage versions, and control who has permission to use each template. This integration is useful for operations teams that want to standardize documents across departments or ensure consistent branding and field requirements.

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 account with library management permissions 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 library_read to view templates, library_write to create and modify templates, library_retention to manage version history, and agreement_read to see how templates are being used. Optional scopes include user_read for permission management.

Available tools​

These tools let you create and organize a centralized library of document templates with consistent form fields, styling, and access controls.

ToolDescription
Create templateUpload a document and convert it into a reusable template
List templatesRetrieve templates from your library with filtering by name or category
Get template detailsView all fields, properties, and metadata for a specific template
Update templateModify template settings, fields, or branding
Delete templateRemove a template from the library
Add template fieldsInsert form fields like text inputs, signatures, or dropdowns
Share templateGrant team members or groups permission to use the template
Create template versionSave a new version of an existing template
Get template version historyView all past versions of a template
Restore template versionRevert to a previous version of a template

Tips​

Use consistent naming conventions for templates (for example, "Contract-NDA-2024") so team members can easily find the right document to use.

Test all form fields and merge field mappings before sharing a template with your team to prevent errors when agreements are created.

Regularly review template usage reports to identify outdated or rarely-used templates that can be archived or retired.

Set folder-level permissions to control which teams can access which templates rather than managing permissions on each template individually.

Create a "template request" process so team members can ask for new templates, helping you maintain a focused library that matches actual business needs.