eSignatures.io
eSignatures.io provides a platform for sending and signing mobile-friendly contracts over the web.
Verdict
Common use cases
- Send NDAs to new hires from Slack
- Generate sales contracts during discovery calls
- Withdraw unsigned agreements before renewal
- Audit active templates across the team
- Add last-minute signers to pending docs
Integration
- Vendor
- eSignatures.io
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
esignatures_io
Tools
- Create Contract
Tool to create a new contract using a specified template and signer details. use after selecting a template when you need to send a contract for signature.
- Create Signer
Tool to create a new signer profile. use when you need to add a signer to an existing signature request.
- Create Template
Tool to create a new template. use when you want to register a reusable contract template after defining document elements.
- Delete Templatedestructive
Tool to delete a specific template by its id. use when you need to remove an unused or outdated template after confirming its id.
- Get Template
Tool to retrieve details of a specific template by its id. use when you need to fetch a template’s metadata after selecting its id.
- List Templates
Tool to retrieve a list of all templates. use when you need to browse available templates before selecting one.
- Withdraw Contract
Tool to withdraw a contract by its id. use when you need to prevent further signing of a contract that hasn't been fully signed.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Search for eSignatures.io and click Connect. 3. Log in to your eSignatures.io dashboard, go to API Settings, and generate a new API key. 4. Paste the key into Switchy's prompt and click Authorize. 5. Return to any Space and type '@eSignatures.io list my templates' to confirm the connection works. 6. If you see your template list, the integration is live — you can now @mention eSignatures.io in any message to create contracts, add signers, or withdraw pending requests. 7. To send your first contract, type '@eSignatures.io create a contract using template [template_id] for signer [name] at [email]' and the MCP will handle the rest.
What teammates see: by default, memories from eSignatures.io are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Templates
@eSignatures.io show me all available templates with their IDs and namesOpen in a Space →
Send NDA for Signature
@eSignatures.io create a contract using template [template_id] for John Doe at john@example.comOpen in a Space →
Add Signer Mid-Flight
@eSignatures.io add a new signer named Jane Smith with email jane@example.com to contract [contract_id]Open in a Space →
Withdraw Pending Contract
@eSignatures.io withdraw contract [contract_id] and confirm it's no longer activeOpen in a Space →
Inspect Template Details
@eSignatures.io get full details for template [template_id] including all configured fieldsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@eSignatures.io list all available contract templates and show me which ones are most recently created
I found 8 templates in your eSignatures.io account. The three most recent are: 'NDA - Standard Employee' (created March 15, 2024), 'Freelance Service Agreement v2' (created March 10, 2024), and 'Equipment Lease Form' (created February 28, 2024). Older templates include vendor agreements, consulting contracts, and a basic employment offer letter. Each template includes pre-configured signature fields and can be used immediately to create new contracts.
This example demonstrates the MCP's ability to retrieve and organize template metadata. The list reflects whatever templates exist in your eSignatures.io account at query time. Useful for auditing available templates before sending contracts, but requires API key authentication with read permissions on templates.
@eSignatures.io create a new contract using the 'Freelance Service Agreement v2' template for signer Jane Smith at jane@example.com
I've created a new contract (ID: ctr_9x4k2m) using the 'Freelance Service Agreement v2' template. An email has been sent to jane@example.com with a signing link. The contract is now in 'awaiting_signature' status. Jane will receive reminders every 3 days until she signs or the contract expires in 30 days. You can track progress or withdraw the contract if needed before all parties sign.
This example shows the MCP's core workflow: template selection followed by contract creation with signer details. This is a write operation that triggers an external email, so verify recipient details before running. The MCP returns a contract ID you can reference later for status checks or withdrawal. Requires API key with contract creation permissions.
@eSignatures.io check all contracts sent in the last 7 days and summarize which ones are still waiting for signatures
Based on recent contract activity, I don't have a direct 'list contracts' tool in this MCP, so I can't retrieve a time-filtered contract list. The available tools focus on template management and individual contract operations (create, withdraw). To track pending signatures, you'd need to maintain contract IDs from creation responses or use eSignatures.io's dashboard directly. I can help create or withdraw specific contracts if you have their IDs.
This example honestly reveals a limitation: the MCP provides template and single-contract operations but lacks bulk contract querying or status filtering. It's designed for workflow automation (create/withdraw specific contracts) rather than reporting. If you need signature status dashboards, you'll rely on eSignatures.io's web interface or a separate integration.
Use-case deep-dives
When eSignatures.io beats DocuSign for contractor paperwork
A 3-person creative agency hires 8-12 freelancers per quarter and needs NDAs, SOWs, and rate sheets signed fast. The eSignatures.io MCP is the right call here because the template tools let you script the entire flow in a Switchy assistant: list templates, pick the NDA, create the contract with the freelancer's email, done. No context-switching to a web UI. The API key auth means one team member sets it up once and everyone shares the assistant. The withdraw tool covers the common case where you send the wrong rate or scope and need to pull it back before signature. If you're sending fewer than 5 contracts a month, the MCP is overkill—just use the eSignatures.io web app. But at freelance-heavy scale, scripting the send-and-track loop in Switchy saves 20 minutes per hire.
Why this MCP works for proposal follow-up at deal velocity
A 6-person B2B sales team closes 15-20 deals per quarter and needs to track which proposals are signed, which are stalled, and which need a nudge. The eSignatures.io MCP plugs into a Switchy assistant that pulls CRM data and checks contract status in one query. The create-contract and create-signer tools let the rep send a proposal from Slack without opening eSignatures.io, and the withdraw tool handles the case where pricing changes mid-negotiation. The limitation: there's no list-contracts or get-contract-status tool in the current set, so you can't query 'show me all unsigned proposals from last week' without building your own tracking layer. If your team needs that visibility, you'll hit the MCP's ceiling fast. But for the send-and-forget workflow—where the signer emails you back when it's done—this MCP cuts the proposal-to-signature time by a day.
When template management justifies the MCP for ops teams
A 4-person ops team manages 40+ vendor agreements with annual renewals and needs to send updated terms each cycle. The eSignatures.io MCP wins here because the template CRUD tools—create, get, list, delete—let you version-control your standard agreements in code, not in a web UI. A Switchy assistant can list templates, confirm you're using the 2025 MSA, create the contract with the vendor's signer details, and log the send in your ops tracker. The delete-template tool matters when you deprecate old terms and don't want them accidentally reused. The trade-off: if your agreements vary wildly per vendor (custom redlines, one-off clauses), templates won't cover it and you're back to manual drafting. But for the 80% of renewals that are copy-paste-send, scripting the flow in Switchy turns a 15-minute task into a 2-minute one.
Frequently asked
What does the eSignatures.io MCP let me do in Switchy?
It connects your eSignatures.io account so AI can create contracts from templates, add signers, and manage signature requests. You can ask AI to send a contract using a specific template, withdraw unsigned contracts, or list available templates. It's useful for teams that send the same agreements repeatedly and want to automate the setup step.
Do I need admin access to connect eSignatures.io?
You need an API key from your eSignatures.io account. Most plans let any user generate an API key in account settings, but check with your account owner if you're unsure. The key grants full access to templates and contracts in that account, so treat it like a password and don't share it outside your team.
Can the MCP edit a contract after someone has signed it?
No. Once a signer completes their signature, the contract is locked. You can withdraw a contract before all parties sign, which cancels the request and prevents further signatures. If you need changes after signing starts, you'll have to withdraw the old contract and create a new one with the correct details.
Why use this instead of logging into eSignatures.io directly?
The MCP saves time when you send similar contracts often. Instead of clicking through the eSignatures.io UI to pick a template and add signers, you tell AI what you need and it handles the API calls. You still log into eSignatures.io to design templates or download signed PDFs, but routine sending happens faster.
Who on the team should connect the eSignatures.io MCP?
Whoever sends contracts most often. The API key ties to one eSignatures.io account, so everyone in Switchy will create contracts under that account's templates and branding. If multiple people need to send contracts, connect one shared account or have each person connect their own key in a separate Switchy workspace.