Skip to main content
These prompts work in any client connected to the Sendforsign MCP server: Claude Code, Claude Desktop, Cursor, ChatGPT through the API or the OpenAI Agents SDK. Replace the parts in [brackets]. Each prompt lists the tools the agent is expected to call and what it should ask you before anyone gets an email. Sending (send_for_signature) and archiving (archive_contract) always need your explicit “yes” in the chat: the server refuses them without confirm: true, and in draft mode refuses them altogether.
Start new connections in draft mode (X-Sendforsign-Agent-Mode: draft). The agent can prepare everything and give you signing links, but cannot email anyone. Switch to send when you trust the flow.

Create

From a template

Tools: list_templates → get_template → create_contract (with templateKey and fields), then fill_placeholders for values you give later. Confirm step: none needed. create_contract makes a draft and emails nobody. The agent should show you which fields it filled (filled), which are still empty (unfilledFields) and which the counterparty will fill (fieldsForRecipients).

From your own text

Tools: create_contract with content (Markdown by default). Confirm step: none; it is a draft. Ask for changes and the agent uses update_contract while the contract has not been sent.

From an attached proposal

Tools: list_templates → get_template → create_contract (template + fields, or content). Confirm step: the agent lists the extracted values and gaps first; you confirm or correct them, then it creates the draft. Nothing is emailed.

Fill and send

Agent fills its fields, the counterparty fills theirs

Tools: list_contracts → get_contract → fill_placeholders with value for your fields and filledBy: "specific_recipient" (with Anna’s recipientKey) or "any_recipient" for hers; add_recipients first if Anna is not on the contract yet. Confirm step: none; no email. The agent shows the field roles.
Tools: add_recipients (returns signingUrl), or list_recipients if she is already added. Confirm step: none; add_recipients never emails. Share each link only with its recipient: the link identifies them. Works in draft mode. See embedded signing.

Send after confirmation

Tools: add_recipients → (summary) → send_for_signature with confirm: true. Confirm step: the agent shows the contract name, the filled values and each recipient with their role and order, and waits. Only after you reply “yes, send” does it call send_for_signature with confirm: true. In draft mode the server refuses and the agent gives you the signing links instead.

Track

What’s waiting for signature

Tools: list_contracts (filters by status, e.g. Sent, Seen, Signed). Confirm step: none; read-only.

Timeline of one contract

Tools: get_contract_timeline (events plus agentActions when the audit log is on). Confirm step: none; read-only.

Who hasn’t signed

Tools: get_contract → get_contract_timeline. Confirm step: none. The agent drafts text; it does not email reminders. Re-sending invitations would be send_for_signature with recipientKeys, which needs your confirmation.

Download the signed PDF

Tools: list_contracts → download_contract_pdf (returns the PDF as base64; agents with file access, such as Claude Code or Cursor, can save it). Confirm step: none; read-only. If the status is not Fully signed yet, the agent should say so.

Embedded and multi-tenant

For products that use Sendforsign for their own customers. See one tenant per customer.

Create a tenant per customer

Tools: create_user (fullname, email, customKey). Confirm step: none; no email. Store the userKey in your product and pass it as X-Sendforsign-User-Key when an agent works for that customer.

List a tenant’s contracts

Tools: list_users → list_contracts with that tenant’s userKey. Confirm step: none; read-only.

Safe modes

Connect in draft mode for review

Connect with X-Sendforsign-Agent-Mode: draft (see the quickstart), then:
Tools: get_connection_info (reports mode: "draft") → list_templates → get_template → create_contract. Confirm step: sending is impossible on this connection; a human reviews the draft and sends it from the Sendforsign app or your product, or shares the link.

Read-only reporting

Connect with X-Sendforsign-Agent-Mode: read_only, then:
Tools: list_contracts → get_contract_timeline. Confirm step: none; every write tool is blocked on this connection.