- Home
- Resources
- Integrations
- Signeasy
Claude Signeasy connectorWhat Claude can do in your Signeasy account.
The Claude Signeasy connector exposes 27 tools. 23 read your account and contract repository, 3 send or cancel something, 1 is unclassified. Below: what Claude checks, what it sends after you confirm, and what Signeasy keeps out of reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can read your Signeasy account
You ask in plain words which contracts are waiting on you, who still has not signed, or what a total comes to across your contracts, and Claude answers from your live Signeasy account. Most tools only look things up. Three of them act, by sending a request, a reminder or a cancellation, and Signeasy says each of those asks for your confirmation first.
Knowing what is blocked. signeasy_pending_for_me and signeasy_pending_for_others split pending documents between those waiting on you and those waiting on someone else, and signeasy_send_reminder emails a reminder to the signers once you confirm.
Asking questions of signed contracts. The repository tools work on key terms extracted from completed documents: signeasy_aggregate_contracts sums or averages a term, signeasy_search_contract_clauses searches the text by clause or concept.
Starting a request from a template. signeasy_create_signature_request sends one from a document or template, after confirmation; Signeasy also lists a preview tool that it says emails nobody.
What Claude does not do: repository answers cover only the Repository section, and the pending-details tool returns no extracted contract terms. Nothing runs by itself, either: Claude acts while it answers you. For steps that fire on their own after a signature, an automation tool fits better, a different trade; the Integrations hub covers that side.
Five terms before you start
The words you will meet while plugging Signeasy into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- Signeasy's own sign-in screen, where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before going through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Signeasy.
Plug Signeasy into Claude in three steps
- 01
Find Signeasy among your connectors
In Claude's settings, open Customize, then Connectors, and look for Signeasy. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first before each member can sign in.
- 02
Start the connection
Click Connect on Signeasy's row and sign in through the window Signeasy opens itself. If the link ever breaks, the fix is to use Disconnect, then plug Signeasy back in from that same row.
- 03
Read the authorization screen
Check Signeasy's authorization screen before you accept. It belongs to Signeasy, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Signeasy account.
The 27 Signeasy tools, sorted by what they do
Signeasy gives Claude 27 tools: 23 that read your account, 3 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it sends or cancels, and one tool no source classifies. Names stay in English, as Claude displays them.
- 23 read
- 3 write
- 1 not documented
Tools index
- signeasy_aggregate_contracts
- signeasy_count_contracts
- signeasy_get_account_info
- signeasy_get_account_summary
- signeasy_get_contract_details
- signeasy_get_contract_field_values
- signeasy_get_document_download_url
- signeasy_get_document_signers
- signeasy_get_pending_details
- signeasy_get_repository_filters
- signeasy_get_template_details
- signeasy_list_document_sources
- signeasy_list_documents
- signeasy_list_expired
- signeasy_list_pending
- signeasy_list_signed
- signeasy_list_templates
- signeasy_list_workspaces
- signeasy_pending_for_me
- signeasy_pending_for_others
- signeasy_query_contracts
- signeasy_search_contract_clauses
- signeasy_signed_this_week
What Claude reads (23)
23 toolsTools that look up your account, envelopes, templates and repository without changing them.
signeasy_aggregate_contracts
Sums, averages or otherwise aggregates one key term across the contracts in your repository, so the answer is a single computed figure.
signeasy_count_contracts
Returns how many contracts match the filters Claude applies: a count, not the documents themselves. It works on the same repository as the other contract tools, and the documents stay untouched.
signeasy_get_account_info
Fetches your Signeasy account details, including subscription status and credits. It reports on the account itself rather than on any document, and only reads it.
signeasy_get_account_summary
Gives a comprehensive summary of the account in one answer, with document counts and recent activity. Where the account-details tool covers subscription and credits, this one looks at what the account holds and what moved lately.
signeasy_get_contract_details
Returns all the key terms extracted for one contract, gathered in a single reply. The other contract tools work across many agreements; this one stays on a single contract from the repository.
signeasy_get_contract_field_values
Lists the distinct values recorded for a key term or a contract type. Knowing which values exist lets Claude filter on a real value instead of guessing how it was written.
signeasy_get_document_download_url
Produces a temporary download link for a contract's document, so you get the file itself rather than a summary.
signeasy_get_document_signers
Shows the signer information attached to a document. Where the pending lists say which documents are waiting, this tool says who is attached to one document in particular.
signeasy_get_pending_details
Opens one specific pending request and returns its envelope and recipient metadata.
signeasy_get_repository_filters
Reveals the fields, operators, contract types and key-term names available in the repository. It describes what can be asked rather than returning any contract.
signeasy_get_template_details
Returns the roles and fields defined in one template. The template list tells you which templates exist; this tool opens one of them to show its structure.
signeasy_list_document_sources
Lists the available document sources: originals, envelopes, signed and pending ones, templates and the repository. Signeasy says it lets Claude pick the right one when you ask to list your documents.
signeasy_list_documents
Brings back your original documents. Signeasy keeps them apart from envelopes, signed and pending documents, templates and the repository, which other tools on this sheet cover.
signeasy_list_expired
Lists the documents that have expired, a status Signeasy keeps separate from pending and from signed documents. It only reads that list, so the documents themselves stay exactly as they are in your account.
signeasy_list_pending
Gathers the signature requests that are still pending. Two other tools split that same waiting list in half, between what waits for your signature and what waits on other signers.
signeasy_list_signed
Returns the documents that are signed and completed, the full set rather than only the latest ones, which a separate tool on this sheet lists on its own.
signeasy_list_templates
Brings up the templates saved in your account, the starting points a signature request can be created from. It lists them without opening their roles and fields.
signeasy_list_workspaces
Lists the repository workspaces you can access, so later queries can be scoped to a named workspace. Workspaces you cannot open yourself do not appear, since Claude works with your own rights.
signeasy_pending_for_me
Picks out the documents waiting for your own signature, the half of the pending list that depends on you. The directory description presents this as seeing which contracts need your action.
signeasy_pending_for_others
Covers the other half of the waiting list: documents held up by other signers rather than by you. The directory description frames it as visibility into who is still pending.
signeasy_query_contracts
Returns a filtered, sorted list of contracts from the repository. Unlike the counting and aggregating tools, it hands back the contracts themselves, in the order requested.
signeasy_search_contract_clauses
Searches contract text by clause or concept rather than by title or by an extracted key term. It reads the wording of the agreements without changing them.
signeasy_signed_this_week
Surfaces the documents signed recently, not the full history of completed ones that the signed-documents list returns. It is a short window on the latest signatures, and it only reads them.
What Claude sends or cancels (3)
3 toolsThree tools that email people or change your account. Signeasy says each asks you to confirm before it runs.
signeasy_cancel_request
Asks you firstCancels or voids a signature request that is still pending.
signeasy_create_signature_request
Asks you firstCreates a signature request from your documents or templates and sends it.
signeasy_send_reminder
Asks you firstSends a reminder email to the signers of a pending request.
Unclassified (1)
1 toolSigneasy describes this tool, but no source says whether it changes your account, so it is not placed with reads or writes.
signeasy_create_signature_request_preview
Signeasy describes it as generating a preview link to review a request before sending, with nobody emailed until you send it yourself. No source says whether it reads or changes your account, so it stays unclassified here.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the conversation, at the moment it counts.
Here the vendor is explicit: Signeasy states that anything sending email or changing your account, such as a reminder or a new signature request, asks you to confirm before Claude carries it out, and that an unconfirmed action does not run. On Team and Enterprise workspaces, owners also decide whether members may skip some prompts and can restrict what the connector may do for everyone. Claude works with the permissions you granted to Signeasy and nothing more.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer is published nowhere, connector by connector: a real gap in the catalogue, not in our research.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can connect one by one. For Signeasy's current status on your account, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing sends a reminder by itself.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's verification badge is not a security audit; Anthropic states on every sheet that it neither chooses a publisher's tools nor guarantees how they behave. This connector is documented only by Signeasy, in its connector documentation updated in September 2026; no Claude help article covers it.
Need help connecting Signeasy to Claude?
A person reads every message.