Skip to main content

12 November

Sendforsign MCP server for AI agents

Any MCP client (Claude, ChatGPT, Cursor, the OpenAI Agents SDK or your own agent) can now work with contracts through the remote MCP server at https://api.sendforsign.com/mcp (Streamable HTTP). New features:
  • 17 tools: templates and their fields, drafts from a template or from Markdown/HTML, filling fields, recipients with signing links, sending for signature, timeline, PDF download, archive, tenants for embedded products
  • Field roles: the agent fills its own fields and leaves the counterparty’s fields to the counterparty
  • Sign in with Sendforsign: AI apps such as Claude, ChatGPT, Claude Code, Cursor and VS Code connect with OAuth 2.1 (dynamic client registration, PKCE) by pasting the URL. On the consent screen the user picks the account, optionally a user the connector is limited to, what the agent may do (drafts only by default) and allowed recipient domains
  • Guardrails for server-side agents set by the integrator in headers: agent modes (read_only, draft, send), confirm: true before any email or archive, a recipient domain allowlist, agent and on-behalf-of identity
  • An audit log of agent actions, returned in the contract timeline (rolling out)
Connect the MCP server · Tools reference · Modes and accountability

Agent skill and AI agents docs

AI+API is deprecated

AI+API (aiapi.sendforsign.com) is replaced by the MCP server and the agent skill. New integrations should use the MCP server. The AI+API page stays available for existing integrations.