Skip to main content

Adobe Sign widgets MCP server

Adobe Sign widgets are embeddable forms that you can place on your website, customer portal, or internal application to let users sign documents without leaving your interface. An AI agent with access to Adobe Sign widgets can create new signing forms, customize branding and fields, generate embed code, track completion rates, and manage widget lifecycles. This integration is useful for customer-facing teams building self-service onboarding flows, HR teams embedding signature forms in employee portals, or sales teams letting customers accept quotes directly from your website.

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 widget creation 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 widget_read to view widgets, widget_write to create and modify widgets, library_read to access templates, library_write to manage templates, agreement_read and agreement_write to manage submissions, and user_read for user information.

Available tools​

These tools let you create, customize, and manage embeddable signing forms that you can integrate into your applications and websites.

ToolDescription
Create widgetBuild a new embeddable signing form
List widgetsRetrieve all widgets with filtering and sorting
Get widget detailsView configuration, fields, and settings for a widget
Update widgetModify branding, fields, or completion behavior
Delete widgetRemove a widget and stop accepting new submissions
Add form fieldInsert text, signature, date, or checkbox fields
Generate embed codeCreate JavaScript or iframe code to embed the widget
Get widget submissionsRetrieve signed documents and form data from completed widgets
Get submission detailsView the signed PDF and all submitted form values
Get widget analyticsCheck completion rate, abandonment rate, and engagement metrics

Tips​

Test your widget thoroughly on mobile devices before deploying — many users will access signing forms from phones or tablets, so responsive design is essential.

Use clear field labels and add help text for non-obvious fields to reduce abandonment and signing errors.

Enable "save draft" so users can pause and resume signing without losing their progress, especially for longer forms.

Customize the completion experience (thank you page, redirect URL, or download prompt) to match your brand and guide users to the next step in your process.

Monitor completion rates and drop-off points regularly — if users abandon at a particular field, consider simplifying or adding clarifying instructions for that section.