Connect AI workflows to agreements with MCP

Use Model Context Protocol (MCP) to connect eligible AI tools and agreement workflows to eSignly, subject to account permissions and usage controls.

What can MCP help you do?

MCP provides a way for a compatible client to use supported eSignly capabilities in an agreement workflow. The available actions depend on your account, role and configuration.

Work with agreements

Connect supported agreement actions to your workflow while keeping documents in the Agreement Workspace where access allows.

Use shared templates

Use eligible template capabilities with the same Template Library and access rules as the web application.

Keep control

Account permissions, usage limits and security controls apply to connected workflows. Review actions before using them in production.

A conceptual example

A team could use a compatible AI client to help find an agreement and review its status, subject to the user’s permissions. The exact steps and available actions depend on the supported client and account configuration; this example is not executable setup guidance.

Getting started

  1. Contact our team about MCP setup and confirm that your client and account support the workflow.
  2. Configure the appropriate credentials and permissions. Protect keys and rotate or revoke them if needed.
  3. Discuss available test and preflight options with the team before enabling live actions.

Test and live capabilities, limits and feature access depend on account configuration. For an integration discussion, contact our team.

Plan the boundary between testing and live actions

Choose the connection around the actions your client needs, rather than assuming that a successful connection authorizes every operation.

Discover and prepare

Use supported tool discovery, safe status reads, sample validation and preflight behavior to understand the workflow. Test keys support these activities without live side effects.

Confirm production access

Live actions remain subject to the applicable plan, permissions, credits, restrictions and Legal Center gates. Review what the client is preparing before enabling a production workflow.

Keep agreement controls together

MCP follows the same Agreement Workspace, Template Library and add-on access rules as web and API access. It does not introduce a separate agreement storage or billing model.

For AI-assisted contract summaries, extraction and questions, review Contract Intelligence. Its add-on eligibility and usage controls still apply when accessed through a connected workflow.

MCP connection questions

Does an MCP connection bypass agreement permissions?

No. MCP uses the same applicable plan, role, document permissions, usage controls and Legal Center gates as other eSignly access paths. A connected client does not receive unrestricted access to agreements.

What is the difference between test and live keys?

Test keys support reading, schema discovery, sample validation and preflight behavior without live side effects. Live keys can support production actions when plan access, permissions, credits and restrictions allow.

Should I choose MCP or the REST API?

Choose MCP when a compatible AI client or agent needs governed agreement operations. Consider the REST API for an application-driven integration. Confirm the actions, client support and account access needed before choosing the connection.

What information helps eSignly investigate a connection problem?

Provide a masked key suffix, timestamp, request ID, status code, tool or endpoint name and a safe error message. Do not send raw credentials, private signing links or full provider payloads.