Skip to main content

Adobe Sign agreements MCP server

Adobe Sign is the trusted e-signature solution that helps businesses send documents for signature and track agreements throughout their lifecycle. An AI agent with access to Adobe Sign agreements can create and send contracts, check agreement status, send reminders to signers, and manage the entire document signing process. This integration is useful for legal teams, sales operations, HR departments, and anyone who needs to automate contract and agreement workflows.

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 API access 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 main scopes you'll use are agreement_read to view agreements, agreement_write to create and modify agreements, agreement_send to send agreements for signature, library_read to access templates, and user_read to get user information. Optional scopes include workflow_read and workflow_write for managing approval workflows.

Available tools​

These tools let you manage the complete agreement lifecycle — from creating and sending documents to tracking status, managing reminders, and downloading signed copies.

ToolDescription
Create agreementSend a document for signature to one or more recipients
Get agreement detailsRetrieve full information about a specific agreement
List agreementsFetch a list of agreements with filtering and sorting options
Send reminderNotify a signer to complete their signature
Cancel agreementRevoke an agreement that hasn't been fully signed
Replace signerSubstitute a new signer for an existing participant
Download documentGet the signed PDF or other document files
Update agreementModify metadata or settings on an agreement
Create from templateGenerate a new agreement using a saved template
Add form fieldsInsert text, signature, date, or checkbox fields into a document

Tips​

Always verify email addresses before sending agreements to avoid bounced invitations and delays in the signing process.

Use templates for agreements you send frequently — they reduce setup time and ensure consistency across documents.

Set appropriate deadlines and enable auto-reminders to keep signings on track without manual follow-up.

Leverage merge fields to personalize each copy of an agreement with recipient-specific information like names, terms, or contract values.

Archive completed agreements regularly and verify that signed copies are downloaded to your document management system for compliance and audit purposes.