Skip to main content

Adobe Sign webhooks MCP server

Adobe Sign webhooks send real-time notifications to your systems whenever important events happen — such as when a signer completes a signature, an agreement is cancelled, or a reminder is sent. An AI agent with access to Adobe Sign webhooks can create and manage webhook subscriptions, configure which events to monitor, test webhook endpoints, and troubleshoot delivery failures. This integration is useful for operations teams that want to automate downstream processes like updating CRM systems or triggering document archival when agreements are signed.

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 Business or Enterprise account with webhook configuration permissions. 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 webhook_read to view webhooks, webhook_write to create and manage webhooks, webhook_retention to access delivery history, agreement_read for agreement context, event_read for event details, and audit_read for compliance logs. Optional scopes include additional event types or filtering options.

Available tools​

These tools let you configure and manage real-time event notifications for agreements, allowing your systems to react automatically to important signing milestones.

ToolDescription
Create webhookSet up a new webhook endpoint to receive notifications for specific events
List webhooksRetrieve all active webhooks with filtering by event type
Get webhook detailsView configuration and delivery status for a specific webhook
Update webhookModify the endpoint URL, authentication, or subscribed events
Delete webhookRemove a webhook and stop receiving notifications for it
Test webhookSend a sample payload to verify the endpoint is working
Get webhook statusCheck recent delivery attempts and success/failure rates
List webhook eventsView all events delivered through a webhook
Resend failed eventRetry delivery of a webhook event that failed
Update event subscriptionChange which event types trigger the webhook

Tips​

Always use HTTPS endpoints for your webhook receivers to ensure that payloads are encrypted in transit.

Start with a small set of critical events (for example, "agreement signed") rather than subscribing to all events, which can create excessive traffic and complicate debugging.

Implement HMAC signature verification to confirm that incoming webhooks are genuinely from Adobe Sign and have not been tampered with.

Log every webhook you receive, including the full payload and timestamp, so you can troubleshoot missed events or re-process failed deliveries.

Set up a dead-letter queue or retry mechanism for webhook failures so that critical events are not lost — Adobe Sign will retry failed deliveries for a limited time, but your application should handle retries gracefully.