# How to send a contract for e-signature from Claude, ChatGPT or Cursor (MCP)

> Connect your AI assistant to eContract over MCP and let it send contracts for signature, chase signers and fetch the signed PDF, in plain language.

Source: https://econtract.online/blog/send-contracts-for-signature-from-ai-agents-mcp · 2026-10-17 · eContract

Most contracts still wait on someone switching tabs: export the PDF, open the e-signature tool, type every signer's email again, then come back a few days later to check who has signed. If you already work with an AI assistant, it can do all of that for you, as long as it can reach your e-signature service.

That is what the **eContract MCP server** is for. MCP (Model Context Protocol) is an open standard that lets AI assistants call tools on other services. Once eContract is connected, you can say *"send this NDA to Alice and Bob for signature"* and the assistant does it.

## What your assistant can do with eContract

The server exposes twelve tools. The ones you will use most:

| Tool | What it does |
| --- | --- |
| `send_contract` | Creates a contract from a PDF/DOCX (inline, by link, or from a template) and sends it to the signers |
| `list_contracts` / `get_contract` | Shows what is waiting, who has signed and what is next |
| `get_signing_links` | Returns each signer's personal link when you prefer to share links yourself |
| `send_reminder` | Re-sends the invitation to people who have not signed yet |
| `download_signed_document` | Fetches the signed PDF once everyone has signed |
| `get_audit_trail` | Returns the signing evidence: who did what, when, from which IP |
| `verify_pdf` | Checks the digital signatures in any PDF |
| `void_contract` | Cancels a contract that is not completed |

Templates (`list_templates`, `get_template`) and an AI summary of a contract (`analyze_contract`) round it off.

Signing itself always stays with people: the assistant can prepare, send and follow up, but it can never sign on someone's behalf.

## Connect in two minutes

The server address is the same for every client:

```text
https://api.econtract.online/mcp
```

You log in with your eContract account through OAuth, so the assistant gets a scoped token instead of your password. For scripts and CI you can use an API key instead.

- **Claude (web and desktop):** add a custom connector with the URL above. Step-by-step: [Claude setup](/mcp/claude).
- **Claude Code:** `claude mcp add --transport http --scope user econtract https://api.econtract.online/mcp`, then log in. See [Claude Code setup](/mcp/claude-code).
- **ChatGPT:** add it as an app in developer mode: [ChatGPT setup](/mcp/chatgpt).
- **Codex CLI:** `codex mcp add econtract --url https://api.econtract.online/mcp` followed by `codex mcp login econtract`: [Codex setup](/mcp/codex).
- **Cursor, VS Code, Gemini CLI** and others: [all clients](/mcp).

## A first contract, start to finish

1. **Ask:** *"Send the attached service agreement to Alice (alice@example.com) and then Bob (bob@example.com) for signature. Alice signs first."*
2. The assistant confirms the title, the document and the signers with you. This matters: sending contacts real people.
3. It calls `send_contract` with `signingOrder: "sequential"`. eContract prepares the document (DOCX files are converted to PDF) and emails Alice her invitation.
4. **Placing signatures:** for each signer the assistant can pass a `signatureAnchor`, a piece of text printed where that person signs, such as `"PARTY A"` or `"ĐẠI DIỆN BÊN A"`. eContract finds the text in the PDF and puts the signature box right below it, under any caption line such as "(Signature, full name)". Without an anchor, signers get their own boxes at the bottom of the last page.
5. A few days later: *"Who still has to sign the service agreement?"* → `get_contract`. *"Remind them."* → `send_reminder`.
6. When it is complete: *"Download the signed copy and the audit trail."*

## Why the signed PDF holds up

Every signature eContract applies is a certificate-based PAdES signature with an RFC 3161 timestamp over the signature value, and every step lands in a hash-chained audit trail. Anyone can check a signed file, without an account, at [verify.econtract.online](https://verify.econtract.online) or through `verify_pdf`. More on this on the [security page](/security).

## Get started

Create a free account, connect your assistant from the [MCP page](/mcp), and send your next contract without leaving the chat.