eSignatures
eSignatures is an electronic signature platform for creating templates, sending contracts, managing signers, and tracking signing workflows.
Verdict
Common use cases
- Draft contracts from templates during client calls
- Add signers and route agreements in Slack threads
- Check signature status without opening another tab
- Iterate on contract templates with legal review
- Send signature requests after deal terms finalize
Integration
- Vendor
- eSignatures
- Category
- other
- Auth
- API_KEY
- Tools
- 28
- Composio slug
esignatures
Tools
- Add Contract Signer
Add a signer to an editable contract without automatically sending a signature request.
- Add Contract Signers
Add a non-empty list of signers to an editable contract by calling the provider's singular endpoint sequentially in request order. Execution is not atomic and stops on the first provider error. The response preserves earlier signer IDs and
- Add Template Collaborator
Create a name-only collaborator who can edit a template. This action does not send an invitation or perform any other external delivery.
- Create and Send Contract
Create a contract from a template or from ad-hoc Markdown and immediately send signature requests to its signers. Supply exactly one of template_id or markdown. This causes external delivery; production sending is usage-priced and requires
- Create Contract Draft
Create a test or production contract draft from a template or from ad-hoc Markdown, without sending signature requests or otherwise delivering it externally. Supply exactly one of template_id or markdown.
- Create Template
Create a reusable Markdown contract template.
- Delete Contract Signerdestructive
Permanently remove a signer from an editable contract. Withdrawn contracts are locked and reject this operation.
- Delete Templatedestructive
Permanently delete a template.
- Duplicate Template
Duplicate a template with a new title plus optional placeholder replacements.
- Get Contract
Get one contract's current status, details, signers, signer field values, and temporary signed-PDF URL when available. Do not poll this tool; use provider webhooks for lifecycle changes. Records older than two weeks may be incomplete.
- Get Contract Content
Return the Markdown content of one contract.
- Get Contract Placeholder Fields
Return the current placeholder replacements for one contract.
- Get Template
Get one template's metadata, placeholder keys, and signer-field IDs.
- Get Template Content
Return the Markdown content of one template.
- Invite Template Collaborator
Invite a collaborator to edit a template. This action sends an external invitation to the required email address and requires explicit confirmation.
- List Template Collaborators
Return all collaborators who can edit one template. The provider exposes no pagination controls.
- List Templates
Return all templates available to the connected account. The provider exposes no pagination controls.
- Preview Contract Content Update
Preview the prospective Markdown from exact find-and-replace edits without mutating the contract.
- Preview Template Content Update
Preview the prospective Markdown from exact find-and-replace edits without mutating the template.
- Remove Template Collaboratordestructive
Remove a collaborator's permission to edit a template.
- Resend Sign Request
Resend a signature request to one signer. This causes external delivery and may incur production usage charges, so explicit confirmation is required. The provider documents this operation, but its external-delivery behavior has not been liv
- Send Draft Contract
Send an existing draft to its signers. This can cause external delivery and production contracts may incur usage charges; explicit confirmation is required.
- Update Contract Content
Apply exact Markdown find-and-replace edits to a contract. This always mutates the contract; use Preview Contract Content Update to inspect the result first.
- Update Contract Placeholder Fields
Update selected placeholder replacements on an unsigned contract.
- Update Contract Signer
Update selected contact, delivery, authentication, or redirect details for a signer without resending the contract. At least one signer update field is required.
- Update Template
Update a template's title and/or labels without changing its Markdown content. At least one of title or labels is required.
- Update Template Content
Apply exact Markdown find-and-replace edits to a template. This always mutates the template; use Preview Template Content Update to inspect the result first.
- Withdraw Contract
Irreversibly withdraw an active unsigned contract so it can no longer be signed. The retained contract remains queryable.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for 'eSignatures' and click Connect. 3. You'll be prompted to paste an API key — log into your eSignatures dashboard, go to Settings > API Access, and generate a new key with read and write permissions. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Choose whether to connect your production or test environment (test is safer for initial setup). 6. Back in any Project, type '@eSignatures list my templates' and send — if you see a list of templates, the connection is live. 7. To invoke a tool, @mention eSignatures in a message and describe what you need (e.g. '@eSignatures create a draft contract from template XYZ').
What teammates see: by default, memories from eSignatures are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Templates
@eSignatures show me all my active contract templates with their IDs and names
Draft NDA from Template
@eSignatures create a test contract draft from template ID 12345 and show me the contract details
Add Signer to Contract
@eSignatures add jane.doe@example.com as a signer to contract ID 67890 with role 'Client'
Send Contract for Signature
@eSignatures create and send a production contract from template ID 12345 with signers john@client.com and sarah@vendor.com
Check Contract Status
@eSignatures get the status and signer details for contract ID 67890
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@eSignatures create a contract from the 'Standard NDA' template, add jane@vendor.com and mike@vendor.com as signers, then send it immediately
Contract created from template 'Standard NDA' (ID: tpl_8x3k). Added two signers: jane@vendor.com and mike@vendor.com. Signature requests sent via email to both parties. Contract ID: ctr_9m2p. Track status at your eSignatures dashboard. Both signers will receive signing links valid for 30 days.
This write example triggers external delivery—emails go out to real people. Always verify signer addresses before running in production. The MCP calls Create and Send Contract, which is not reversible once sent. Use Create Contract Draft first if you want to review before sending.
@eSignatures pull the three most recent fully executed contracts and draft a one-paragraph summary of common terms across them
Retrieved contracts ctr_7k1m (MSA with Acme Corp), ctr_6j9n (Consulting Agreement with freelancer), and ctr_5h8p (SaaS subscription with CloudVendor). Common terms: all three include 30-day payment windows, mutual confidentiality clauses, and termination-for-convenience with 15–30 day notice. The MSA and consulting agreement both specify governing law as Delaware; the SaaS contract uses California law.
This synthesis example pairs the MCP's contract-fetch capability with the AI's reasoning to surface patterns. Useful for compliance checks or template refinement. Accuracy depends on contract text quality; always verify extracted terms against source documents for legal decisions.
Use-case deep-dives
When eSignatures MCP beats manual send for hiring sprints
A 6-person startup hiring three contractors in one week needs NDAs, service agreements, and W-9s signed before work starts. The eSignatures MCP wins here because you can script the entire flow: create contract drafts from templates, add signers in batch, and send signature requests in one Switchy conversation instead of clicking through a web UI three times per hire. The MCP's 28 tools cover the full lifecycle—draft creation, signer management, template reuse—so your ops lead doesn't context-switch between Slack, your ATS, and the eSignatures dashboard. The threshold: if you're hiring fewer than two people per month, the manual UI is faster than learning the MCP's tool names. Above that cadence, the scripted workflow pays back in week one.
Why this MCP falls short for multi-stage quote reviews
A 12-person sales team needs proposals reviewed by legal, finance, and the VP before the customer sees them. The eSignatures MCP handles the final signature step cleanly—create the contract, add the customer as signer, send—but it doesn't orchestrate the internal approval chain that happens before that. You'd need a separate workflow tool (Linear, Asana, or a custom script) to route the draft through your three internal reviewers, then call the MCP only at the end. If your approval process is lightweight (one person signs off in email), the MCP works. If you need audit trails, conditional routing, or parallel reviews, you're duct-taping two systems together. For pure signature collection after approvals are done, it's a clean fit.
When the MCP makes template versioning manageable at scale
A 20-person professional services firm maintains 40 contract templates (SOWs, MSAs, change orders) that legal updates quarterly. The eSignatures MCP's template tools—create, delete, add collaborators—let you version-control those templates in a Git-like flow without leaving Switchy. Your legal ops person can create a new template revision, test it with Create Contract Draft, compare the Markdown diff against the old version, then delete the outdated template once the new one is live. The collaborator tool means your three contract owners can all edit templates without sharing one login. The trade-off: if your templates have complex conditional logic or fillable fields beyond Markdown's scope, you'll hit the MCP's formatting ceiling and need the vendor's visual editor. For text-heavy, low-branching templates, this is the fastest way to keep 40 documents in sync.
Frequently asked
What does the eSignatures MCP do in Switchy?
It lets your AI agents create contracts from templates or Markdown, add signers, and send signature requests directly through the eSignatures API. Agents can also manage templates, add collaborators, and delete signers from editable contracts. You control whether contracts are test drafts or production sends.
Do I need an eSignatures API key to connect this MCP?
Yes. The MCP uses API key authentication, so you'll need to generate one from your eSignatures account settings. Whoever connects it should have permission to create contracts and templates in your workspace. The key is stored encrypted in Switchy and scoped to the tools you enable.
Can the MCP edit a contract after it's been sent?
No. Once you use Create and Send Contract, the contract is locked and delivered to signers. You can only add or delete signers on editable drafts. If you need to change a sent contract, you'll have to withdraw it in the eSignatures dashboard and create a new one.
Why use this MCP instead of the eSignatures web app?
The MCP lets agents generate contracts from structured data in your workspace without manual copy-paste. If you're already drafting terms in Notion or Slack, an agent can turn that into a signature-ready contract in one step. For one-off sends or heavy template editing, the web app is still faster.
Who on my team should connect the eSignatures MCP?
Whoever owns your eSignatures account and can issue API keys. That person's permissions determine what the MCP can do. If you want agents to send production contracts, connect it with a production key. For testing workflows, use a sandbox key first.