Send for signature
Create a contract from a PDF, DOCX, link or template and send it to one or many signers, in order or in parallel. Get signing links, send reminders or cancel.
send_contractget_signing_linkssend_remindervoid_contract
Remote MCP server
Let your AI agent send contracts for e-signature
eContract has a remote MCP server. Connect Claude, ChatGPT, Codex, Cursor or any MCP client and ask it to prepare a contract, send it for signing, follow its status and fetch the signed PDF, right from the chat.
MCP server URL (Streamable HTTP)
https://api.econtract.online/mcpWhat your agent can do
12 tools cover the whole contract workflow. A person always signs.
Track and archive
List contracts, see who has signed, download the signed PDF and get the full audit trail.
list_contractsget_contractget_audit_traildownload_signed_document
Use templates
Find workspace templates and the fields to fill in before sending.
list_templatesget_template
Verify and analyse
Check the digital signatures in any PDF and get an AI summary of a contract: parties, value, duration and risks.
verify_pdfanalyze_contract
Setup guides
Step-by-step setup for the most used AI assistants and agents.
ClaudeAnthropic · Chat assistantSetup guide Claude CodeAnthropic · Terminal agentSetup guide ChatGPTOpenAI · Chat assistantSetup guide CodexOpenAI · Terminal agentSetup guide CursorAnysphere · Code editorSetup guide VS Code (GitHub Copilot)Microsoft · Code editorSetup guide Gemini CLIGoogle · Terminal agentSetup guide Muse CodeMeta · Terminal agentSetup guide OpenClawOpenClaw · Autonomous agentSetup guide Hermes AgentNous Research · Autonomous agentSetup guide
Using another client? Any MCP client that supports Streamable HTTP and OAuth 2.1 can connect to https://api.econtract.online/mcp.
Two ways to connect
Sign in with OAuth (recommended)
Your AI client opens the eContract sign-in page, you choose a workspace and approve the permissions. The client renews its access by itself, so you sign in once. You can revoke access at any time.
API key for unattended agents
For agents that run on a server, on a schedule or in a script, with no one there to sign in. Create a key with only the permissions it needs and send it as a Bearer token. A key works until you revoke it.
Create an API keyBuilt for safe automation
A person always signs
Agents prepare and send contracts, but they cannot sign or decline for anyone: each signer signs through their own link after confirming a code sent to their email.
Only the permissions you grant
OAuth access and API keys are limited to the scopes you approve, in one workspace, and can be revoked at any time.
Every action on the record
Actions taken through MCP appear in the contract’s audit trail, and signed PDFs carry certificate-based signatures that anyone can verify.
Frequently asked questions
What is the eContract MCP server?
It is a remote Model Context Protocol server at https://api.econtract.online/mcp. AI assistants and agents that support MCP connect to it and get tools to create, send, track and verify contracts in your eContract workspace.
Does it cost anything?
No. The MCP server is part of eContract, which is free for now with fair-use limits.
Can an AI agent sign a contract for me?
No. Agents can prepare and send contracts and share signing links, but every signer signs personally after confirming a code sent to their email.
Which permissions does an agent get?
Only the scopes you approve when you connect, such as reading contracts, sending contracts or using AI analysis, and only in the workspace you choose. You can revoke the access or the API key at any time.
Which AI clients are supported?
Any client that supports remote MCP servers over Streamable HTTP, including Claude, ChatGPT, Codex, Cursor, VS Code, Gemini CLI, Muse Code, OpenClaw and Hermes Agent.