MCP

Signing shouldn't mean switching tabs. The Signeasy MCP server lets you work with your Signeasy account directly inside Anthropic's Claude.

Using the Model Context Protocol (MCP), Claude can look up your account, find and track documents, send reminders, start signature requests, and query your AI-analyzed contract repository, all from a normal conversation.

This guide walks you through connecting Signeasy to Claude, authorizing access to your account, and getting started with example prompts.

How it works

The Signeasy MCP server acts as a secure bridge between Claude and Signeasy. When you add it as a connector, Claude discovers the server's capabilities and asks you to sign in to Signeasy. You authorize the connection once through Signeasy's own login screen, and from then on Claude can call Signeasy on your behalf using the permissions you granted.

📘
Your credentials stay with Signeasy
Your Signeasy credentials are never shared with Claude. Authentication uses OAuth 2.0 with PKCE, and the server passes your Signeasy access token through directly. It stores no passwords and keeps no copy of your data.

Before you begin

To connect Signeasy to Claude, you'll need:

A Signeasy account with an active plan.

If you're not sure whether your plan supports connectors, check with your Claude workspace owner.

Connect the Signeasy connector in Claude

Open Claude and go to Settings.
Select Connectors.
Search for Signeasy in the connector directory, then add it.

Authorize access to your Signeasy account

The first time you use the connector, Claude asks you to sign in to Signeasy:

When prompted, select Connect or Authorize.
You'll be redirected to Signeasy's sign-in page. Log in with your Signeasy credentials.
Review the permissions the connector is requesting and approve them.
Once authorized, you're returned to Claude and the connector is ready to use.

You only need to do this once. Claude keeps the connection active until you disconnect it or the authorization expires.

Permissions requested

The connector requests only the access it needs to help you. Depending on how it's configured, this may include reading your profile and account details, reading your documents and signature requests, sending reminders, and creating signature requests. Signeasy's OAuth screen shows the exact permissions before you approve.

What you can do

Once connected, Claude can use the following Signeasy tools on your behalf.

Account

Tool	What it does
`signeasy_get_account_info`	Get your account details, including subscription status and credits.
`signeasy_get_account_summary`	Get a comprehensive summary of your account, document counts, and recent activity.

Documents and signature requests (Envelopes section)

These tools cover documents in your account's Envelopes section.

Tool	What it does
`signeasy_list_documents`	List your original documents.
`signeasy_list_envelopes`	Lists signature requests/envelopes of any status across every workspace the user can access. Use for cross-workspace or mixed-status listings; for a single status of the user’s own requests, the focused tools `signeasy_list_pending`, `signeasy_list_signed`, `signeasy_list_expired`) are preferred. Optional `workspace_ids` (from `signeasy_list_workspaces`), status `pending_on_me`, `pending_on_others`, `complete`, `draft_merged`, `canceled`, `recipient_declined`, `expired`), `sort_by` `name`, `last_modified_at`, `created_at`, `expires_at`), `order`, `size`, `offset`. Omitting `workspace_ids` lists across all accessible workspaces; omitting `status` returns all statuses.
`signeasy_list_pending`	List pending signature requests.
`signeasy_pending_for_me`	List documents waiting for your signature.
`signeasy_pending_for_others`	List documents waiting on other signers.
`signeasy_list_expired`	List expired documents.
`signeasy_list_signed`	List signed and completed documents.
`signeasy_signed_this_week`	List documents signed recently.
`signeasy_get_pending_details`	Get details of a specific pending request.
`signeasy_get_document_signers`	Get signer information for a document.
`signeasy_list_templates`	List your templates.
`signeasy_get_template_details`	Get the roles and fields for a specific template.
`signeasy_list_document_sources`	List the available document sources — originals, envelopes, signed and pending, templates, and repository — so Claude can pick the right one when you ask to "list my documents."

Actions

Tool	What it does
`signeasy_approve_request`	Approves a signature request that is pending the user's approval, where they were added as an approver. Approvers review before signers get access; once all approvers approve, the request moves on to the signers. Valid only while the envelope is awaiting approval. Takes `pending_id` (required) and an optional `message` note recorded in the audit trail.
`signeasy_decline_request`	Declines a signature request sent to the user, as either a signer or an approver. Declining rejects the whole envelope: it moves to `recipient_declined` and no one else can sign it. This is the recipient's own decline — to call off a request the user sent, use `signeasy_cancel_request`. Takes `pending_id` and a required `message` decline reason, which is recorded in the audit trail and shared with the sender.
`signeasy_send_reminder`	Send a reminder email to signers of a pending request.
`signeasy_cancel_request`	Cancel or void a pending signature request.
`signeasy_create_signature_request`	Create and send a signature request from documents or templates.
`signeasy_create_signature_request_preview`	Generate a preview link to review a request before sending — nobody is emailed until you send it yourself.

Contract repository (AI)

Query AI-analyzed contracts by their extracted key terms and document text. These tools strictly cover your account's Repository section, which holds documents completed through Signeasy and external completed documents.

Tool	What it does
`signeasy_get_pending_contract_terms`	Returns AI-extracted key terms for one in-flight/pending signature request, by the `pending_id` returned from the pending tools. Use it for a specific pending contract's value, dates, parties, or other key terms. `signeasy_get_pending_details` does not return these; it only returns envelope and recipient metadata.
`signeasy_query_pending_contracts`	Queries pending signature requests by AI-extracted contract key terms in a single composite workflow — for questions like "which pending documents are worth over $100?" or pending contracts filtered by dates, parties, status, or value. It lists pending envelopes, batch-fetches their contract terms, applies AND filters, and reports unprocessed or unavailable pending IDs separately. Optional `scope` (`all`, `for_me`, `for_others`; default `all`), `filters` (up to 10 items of `{key_name, operation, value}`), and `currency` (e.g. `USD` for `$`). Supported filter operations: `eq`, `neq`, `gt`, `gte`, `lt`, `lte`, `contains`, `notContains`, `startsWith`, `endsWith`, `in`, `notIn`, `is_null`, `is_not_null`, `is_not_empty`.
`signeasy_get_repository_filters`	Discover available fields, operators, contract types, and key-term names.
`signeasy_query_contracts`	Get a filtered, sorted list of contracts.
`signeasy_count_contracts`	Count contracts matching your filters.
`signeasy_get_contract_field_values`	List distinct values for a key term or contract type.
`signeasy_aggregate_contracts`	Sum, average, or otherwise aggregate a key term across contracts.
`signeasy_search_contract_clauses`	Search contract text by clause or concept.
`signeasy_get_contract_details`	Get all extracted key terms for one contract.
`signeasy_get_document_download_url`	Get a temporary download link for a contract's document.
`signeasy_list_workspaces`	List the repository workspaces you can access, so queries can be scoped to a named workspace.

📘
Actions confirm before they run
Anything that sends email or changes your account, such as sending a reminder or creating a signature request, asks you to confirm before Claude carries it out.

Example prompts

Once the connector is set up, just ask Claude in plain language.

Account and documents

"How many envelope credits do I have left?"
"Give me a summary of my Signeasy account."
"Show me my pending signature requests."
"What documents need my signature?"
"List everything I signed this week."
"What templates do I have available?"

Actions

"Send a reminder for the contract waiting on Jordan."
"Cancel the pending request for the vendor agreement."
"Start a signature request from my NDA template for [email protected] — let me preview it first."

Contract repository (AI)

"How many NDAs do I have?"
"What's the total value of my service agreements?"
"Show me the contracts expiring soonest."
"Which contracts mention force majeure?"
"Which contracts involve Acme Corp?"

Troubleshooting

You're not asked to sign in, or authorization fails.
Remove and re-add the connector, then try again. Make sure you're signing in with the Signeasy account you intend to use.

Claude says it can't find a document or action.
Confirm the connector is enabled for your conversation and that your Signeasy plan and permissions include what you're asking for. Some actions, such as creating signature requests, require the matching permission to be granted during authorization.

An action didn't go through.
Actions that email people or change your account ask you to confirm first. If you didn't confirm, the action won't run — just ask Claude again and approve when prompted.

Get help

For questions about your Signeasy account or plan, email Signeasy support at [email protected]. For help with the connector or self-hosting the Signeasy MCP server, reach out to your organization's administrator.