---
title: "Send contracts with an AI agent"
description: "Connect Claude, ChatGPT, or Cursor to the SignatureAPI MCP server, draft a contract envelope in test mode, check it, and send it live once you approve."
canonical: "https://signatureapi.com/docs/ai-toolkit/guides/agent-sends-contract"
source: "https://signatureapi.com/docs/ai-toolkit/guides/agent-sends-contract.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T13:19:17Z"
---

# Send contracts with an AI agent

Connect Claude, ChatGPT, or Cursor to the SignatureAPI MCP server, draft a contract envelope in test mode, check it, and send it live once you approve.

_Last verified against API version 1.18.0._

This guide takes you from an empty chat to a signed contract, with an AI app doing the API work through the [SignatureAPI MCP server](https://signatureapi.com/docs/ai-toolkit/mcp/overview). You check every envelope in test mode first, and nothing reaches a real signer until you say so.

You need a SignatureAPI account ([sign up](https://accounts.signatureapi.com/sign-up) if you don't have one) and one of Claude, ChatGPT, or Cursor.

1. **Connect your AI app**

   #### Claude

   In Claude Desktop or Claude.ai, open **Customize** → Connectors → **Add custom connector**, and paste the server URL:

   ```text
   https://mcp.signatureapi.com/mcp
   ```

   Sign in to SignatureAPI in the window that opens, choose the organization, and click **Allow**.

   #### ChatGPT

   SignatureAPI is a published ChatGPT app. Open the app directory, search for **SignatureAPI**, click **Connect**, and complete the sign-in.

   #### Cursor

   Add the server to `.cursor/mcp.json` in your project:

   ```json .cursor/mcp.json
   {
     "mcpServers": {
       "signatureapi": {
         "url": "https://mcp.signatureapi.com/mcp"
       }
     }
   }
   ```

   Then open **Settings → MCP** and complete the sign-in next to the server.

   [Connecting clients](https://signatureapi.com/docs/ai-toolkit/mcp/connecting-clients) covers every other client.

2. **Check which account the agent acts for**

   Ask:

   ```text
   Which SignatureAPI account are you connected to, and can you use live mode?
   ```

   The agent calls `whoami`. It names the account and reports `modes.live`: whether this session may send live envelopes. Live mode needs an active account and an organization role with live-mode access.

3. **Draft the envelope in test mode**

   Ask for the envelope you want. This example uses a sample agreement with two signature placeholders, one per signer:

   ```text
   In test mode, send the Service Agreement at
   https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/acme-service-agreement.pdf
   to Jane Doe (jane.doe@example.com) as the client and John Smith
   (john.smith@example.com) as the provider. Jane signs at [[client_signs_here]]
   and John at [[provider_signs_here]]. Both can sign at the same time.
   Summarize the envelope before you create it.
   ```

   The agent calls `create_envelope`. Every call is in [test mode](https://signatureapi.com/docs/api/test-mode) unless it asks for live, and test mode sends no email. For your own file, attach it to the chat (ChatGPT, Claude) or give the agent a path it can upload (Cursor).

4. **Check it as the signer would**

   Ask:

   ```text
   Show me the signing request Jane would receive and give me her test signing link.
   ```

   The agent finds the request with `list_emails` and reads its `ceremony_url` with `get_email`. Open the link and sign as Jane to see the ceremony. Then ask "What happened on that envelope?", and the agent lists the events with `list_events`.

5. **Send it live after you approve**

   A test envelope never becomes a live one. When the draft looks right, ask for a new envelope in live mode:

   ```text
   The test looks right. Create the same envelope in live mode.
   ```

   Most clients ask you to confirm the tool call: `create_envelope` is marked destructive because, in live mode, it emails real people. Read the summary before you approve it.

6. **Follow it to the signed document**

   ```text
   Tell me when both signers are done, then give me the signed document.
   ```

   The agent waits for new events with `list_events` and its `wait_seconds` option. Once the envelope completes, `get_deliverables` returns the signed PDF with a download link valid for about an hour.

## Building an agent for your own customers

The hosted MCP server connects one person's agent to their own account. To run an agent that sends contracts for many customers, build its tools on the [REST API](https://signatureapi.com/docs/api/overview), with your backend holding the API key. See [Authorization](https://signatureapi.com/docs/ai-toolkit/mcp/authorization#service-provider-running-an-agent-on-behalf-of-users).

## Next steps

- [Send an NDA to a list](https://signatureapi.com/docs/ai-toolkit/recipes/nda-batch): one prompt for several signers.
- [Agent safety](https://signatureapi.com/docs/ai-toolkit/guides/agent-safety): keep live sends under human approval.
- [Tools and resources](https://signatureapi.com/docs/ai-toolkit/mcp/tools): every tool the agent can call.
