update_contract_content on a live contract is the capability a PDF workflow cannot offer, and it is what makes the amendment path — draft, fill, send, amend — one conversation instead of four. The signer tools matter as much: adding a signer and re-sending their request are separate calls, so a stalled signature is fixed without touching the document.
A server over the eSignatures.com API. Contracts are Markdown rather than fixed PDFs, so an agent can write the body, fill the placeholders, send it for signature, and still change it after it has gone out.
- create_contract to draft for review or send outright; withdraw_contract to pull an active one back, delete_contract for a draft or test contract
- query_contract for status, query_contract_content for the body, list_recent_contracts for what is in flight
- update_contract_content to rewrite the body of a contract that is already active
- query_contract_placeholder_fields and update_contract_placeholder_fields for the filled-in values
- add_contract_signer, update_contract_signer and delete_contract_signer for the signer list
- resend_contract_signer_request to send or re-send one signer's request
- create_template, update_template, update_template_content, query_template, query_template_content, list_templates and delete_template for reusable contracts
- add_template_collaborator to give a colleague access to a template
An eSignatures.com account — the server works against that account's API on your behalf, so whatever the account can send, an agent holding the connection can send.
One command plus a key — uvx mcp-server-esignatures, then supply credentials