Contract and template management for drafting, reviewing, and sending binding contracts.
Esignatures mcp server connects ESignatures to AI assistants that speak the Model Context Protocol. Contract and template management for drafting, reviewing, and sending binding contracts.
Traditional eSignature tools lock you into rigid, static PDF files. eSignatures.com takes a different approach — contracts remain fully editable, Markdown-based content throughout their entire lifecycle, making them effortless for developers, automation systems, and AI agents to create, understand, modify, and manage.
Once connected, the assistant can call these 14 tools directly:
create_contract — Contractsquery_contract — Contractswithdraw_contract — Contractsdelete_contract — Contractslist_recent_contracts — Contractsadd_contract_signer — Signersupdate_contract_signer — Signersresend_contract_signer_request — Signersdelete_contract_signer — Signersquery_contract_placeholder_fields — Placeholdersupdate_contract_placeholder_fields — Placeholdersquery_contract_content — Contentupdate_contract_content — Contentcreate_template — TemplatesSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before the server will start you need to supply one environment variable: ESIGNATURES_SECRET_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. ESignatures sits in that group, and the shape of its toolset — create_contract, query_contract, withdraw_contract among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| create_contract | Contracts |
| query_contract | Contracts |
| withdraw_contract | Contracts |
| delete_contract | Contracts |
| list_recent_contracts | Contracts |
| add_contract_signer | Signers |
| update_contract_signer | Signers |
| resend_contract_signer_request | Signers |
| delete_contract_signer | Signers |
| query_contract_placeholder_fields | Placeholders |
| update_contract_placeholder_fields | Placeholders |
| query_contract_content | Content |
| update_contract_content | Content |
| create_template | Templates |
"mcpServers": {
"mcp-server-esignatures": {
"command": "uv",
"env": {
"ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
},
"args": [
"--directory",
"/your-local-directories/mcp-server-esignatures",
"run",
"mcp-server-esignatures"
]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ESIGNATURES_SECRET_TOKEN | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.