Skip to main content
The Sendforsign MCP server is a remote server over Streamable HTTP:
There are two ways to connect:
  • Sign in with Sendforsign (OAuth) — for AI apps people use: Claude, ChatGPT, Claude Code, Cursor, VS Code. Paste the URL, sign in, and choose on the consent screen which account the app may use and what it may do. No API key is copied anywhere.
  • API key in headers — for server-side agents you run yourself, where your code sets the account and the guardrails per connection.

Connect an AI app

Every client below follows the same three steps:
  1. Add the server URL https://api.sendforsign.com/mcp.
  2. Sign in to Sendforsign in the browser window that opens (or create an account).
  3. On the consent screen, choose:
    • Account — the client (clientKey) the app works in, and optionally a user (tenant) inside it. If you pick a user, the connector can only act as that user and cannot list or create users. Without one, it works at the account level and can address any user of the account.
    • What the agent may do — read only, create drafts (the default) or send for signature. Even with send, every email still needs your explicit approval in the chat (confirm: true).
    • Allowed recipient domains (optional) — the app cannot send contracts to anyone outside them.
You can change these later only by disconnecting and connecting again. See modes and accountability for what each choice means.
In Claude on the web or desktop:
  1. Open Settings → Connectors → Add custom connector.
  2. Name it Sendforsign and paste https://api.sendforsign.com/mcp.
  3. Click Connect, sign in to Sendforsign and approve the consent screen.
In a chat, enable Sendforsign from the tools menu. On Team and Enterprise plans, an owner may have to add the connector for the organization first.

Try it

Ask the agent:
What can you do with Sendforsign on this connection?
It calls get_connection_info and tells you its mode, account and allowed domains. Then:
List my templates. Draft an NDA from the NDA template for Acme Ltd, signer Anna Smith, anna@example.com. Show me what you filled in and the signing link. Don’t send it yet.
The agent uses list_templates → get_template → create_contract, returns a draft with a signingUrl and lists the fields left for the counterparty. Nobody is emailed until you approve and the agent calls send_for_signature with confirm: true on a connection allowed to send. More in the prompt library.

Server-side agents (API key)

For agents that run in your backend (your own product’s assistant, a workflow, a scheduled job), authenticate with your API key and configure each connection with headers. Your code, not a consent screen, decides the account, tenant, mode and allowed domains, so you can open one connection per customer of your product.

Get your keys

  1. Sign up at app.sendforsign.com and open the API Keys tab of the dashboard.
  2. Copy your API key (X-Sendforsign-Key).
  3. Copy a client key (clientKey) — the account space the agent works in. If you embed Sendforsign for several customers, create a client per customer and use its key.
An API key gives full access to your account. Keep it out of prompts, repositories and chat transcripts; put it in environment variables or a secret store. Start new integrations with X-Sendforsign-Agent-Mode: draft so the agent cannot email anyone until you are ready.
Recommended on top: X-Sendforsign-Agent (a name for this agent), X-Sendforsign-On-Behalf-Of (the person or company it acts for), X-Sendforsign-Agent-Mode and X-Sendforsign-Allowed-Domains. Note that the header default mode is send, unlike the consent screen. See the headers reference.
agent.py
With the Responses API hosted MCP tool, pass the same headers and keep approvals on:

Troubleshooting