Signeasy

Track contracts, query an AI-analysed repository, send signature requests.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Signeasy connector does

The Signeasy MCP server connects a Signeasy e-signature account to Claude, ChatGPT and any MCP-compatible agent. It tracks who has signed and who has not, queries an AI-analysed contract repository by extracted key terms, and sends signature requests and reminders. Sign-in is OAuth 2.0 with PKCE across ten named scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Signeasy tools (27)

  • signeasy_aggregate_contracts
  • signeasy_cancel_request
  • signeasy_count_contracts
  • signeasy_create_signature_request
  • signeasy_create_signature_request_preview
  • 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_send_reminder
  • signeasy_signed_this_week

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's directory under-lists this server by five tools. All 27 listed names appear in Signeasy's docs; five documented names do not appear in the directory, including signeasy_approve_request and signeasy_decline_request. Size the connector from Signeasy's documentation, not the listing.
  • Sending is not recallable. Three tools email counterparties, and the only response to a mistaken send is a cancellation that emails them again. Do not blanket-approve signeasy_create_signature_request.
  • Envelope credits are consumed and nothing here reports them mid-flight. signeasy_get_account_info is documented as returning subscription status and credits, so an accounting tool does exist — but nothing forces an agent to check it before sending, and Signeasy's FAQ confirms exhausted credits restrict the envelope endpoints. We found no published per-envelope price, so the cost of a run is not predictable from the docs.
  • Two granted scopes exceed the tool surface. template:manage includes delete and rename; original:create includes document import. No tool uses either capability.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or vendor safety hint is published here. The parameter descriptions we cite come from Signeasy's documentation, not from the server.
  • Some capabilities are plan-gated. Signeasy documents recipient OTP authentication, requested attachments and signer groups as API Advanced Plan features, and caps envelopes at 45 recipients and documents at 25 MB.
  • Rate limits are global and tight. 80 requests per minute with a 20-per-10-seconds burst limit, returning HTTP 429.
  • The RFC 9728 descriptor is served as a catch-all. Requesting /.well-known/oauth-protected-resource/ with a nonsense suffix returns the identical body, so the path alone proves nothing. The 401's www-authenticate header naming that exact URL is what makes the descriptor authoritative here.

Frequently asked questions

Can the Signeasy connector email a counterparty?

Yes, by three separate tools. signeasy_create_signature_request emails signers, signeasy_send_reminder emails whoever has not yet signed, and signeasy_cancel_request voids the request and notifies people too. Signeasy's API docs confirm each sends email. None of those emails can be recalled once the call returns.

How many tools does the Signeasy MCP server have?

Anthropic's directory lists 27, and Signeasy's own MCP documentation describes 32. All 27 directory names appear in the docs, so the gap runs one way: the directory under-lists by five. Two of the five change state — signeasy_approve_request releases a request to its signers and signeasy_decline_request kills the envelope outright — so the directory omits exactly the terminal actions a reader most needs to see.

Does Claude ask before Signeasy sends a signature request?

Signeasy states that anything emailing people or changing the account asks you to confirm first. That prompt covers the call, not its consequences. Approving a create_signature_request means an email leaves for a named counterparty immediately, and nothing in the tool surface unsends it — only a cancel that emails them again.

What OAuth scopes does the Signeasy MCP server request?

Ten, and they are real application scopes rather than identity claims. The resource descriptor lists user:read, original:read, original:create, rs:read, rs:create, rs:update, signed:read, template:manage, repository:read and offline_access. Crucially rs:create and rs:read are separate, so a read-only grant is genuinely possible here.

Can the Signeasy connector delete a document?

No tool among the 32 documented names carries a delete verb, but one requested scope grants deletion anyway. Signeasy's scopes table states template:manage grants read, list, rename and delete access to all your templates, while only two read-only template tools exist. The grant is wider than the tool surface uses.

What is the difference between cancelling and declining in Signeasy?

Cancel is the sender's action and decline is the recipient's. signeasy_cancel_request voids a request you sent, triggering Signeasy's rs.voided event. signeasy_decline_request rejects a request sent to you, moving the envelope to recipient_declined so nobody else can sign it. Both are terminal and neither appears reversible.

Why does the Signeasy MCP endpoint URL end in /sse?

The path is named /sse but the transport is streamable HTTP, which Anthropic's directory also records. A POST initialize to https://mcp.signeasy.com/mcp/sse returned an HTTP 401 JSON body rather than an event stream on 2026-08-22. Use the URL exactly as published; the suffix does not mean legacy SSE transport.

Are there rate limits on the Signeasy API?

Yes. Signeasy documents 80 requests per minute globally, a burst limit of 20 requests per 10 seconds, and HTTP 429 with Too Many Requests when you exceed either. Signeasy recommends waiting a minute before retrying. Its sandbox separately caps envelope creation at 50 per hour.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Signeasy to work.

Connect Signeasy once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.