> ## Documentation Index
> Fetch the complete documentation index at: https://sendforsign.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog 2026

> What's new in Sendforsign in 2026: the remote MCP server for AI agents, the agent skill, the AI agents docs section and the deprecation of AI+API.

## 18 November

### Fields in the agent's text and PDF contracts over MCP

* `create_contract` and `update_contract` turn `{{Name}}`, `{{Name=Value}}`, `{{Name@any}}` and `{{Name@email}}`
  markers into fields with the right owner. See [MCP tools](https://sendforsign.com/docs/ai-agents/tools.md#create_contract).
* New tools `create_pdf_contract` (a PDF by https URL or base64) and `place_pdf_fields` (signature, date signed,
  full name, email and text fields, placed in percent of the page). The server now has 19 tools.
* The MCP server is listed in the official MCP registry as `com.sendforsign/mcp`.

### Field values are inserted as text

Field values written into a contract body (placeholder `update`, contract `create`/`update` with placeholders) are
now HTML-escaped, so a value can no longer add markup to the document. A value such as `Smith & Co` looks the same as
before. A field whose value is cleared now shows its `{{{name}}}` token instead of nothing, as in the editor.

## 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](https://sendforsign.com/docs/ai-agents/mcp-quickstart.md) · [Tools reference](https://sendforsign.com/docs/ai-agents/tools.md) ·
[Modes and accountability](https://sendforsign.com/docs/ai-agents/accountability.md)

### Agent skill and AI agents docs

* A new [AI agents](https://sendforsign.com/docs/ai-agents/overview.md) section with recipes, a [prompt library](https://sendforsign.com/docs/ai-agents/prompts.md) and the
  headers and tools reference
* A [Sendforsign agent skill](https://sendforsign.com/docs/ai-agents/skills.md) (`SKILL.md`) for Claude Code, Claude apps, Codex and other agents
* [`/llms.txt`](https://sendforsign.com/docs/llms.txt) and [`/llms-full.txt`](https://sendforsign.com/docs/llms-full.txt)
  for language models
* Placeholder docs now cover `fillingType` (who fills a field) and `externalRecipientKey`

### 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](https://sendforsign.com/docs/ai-agents/mcp-quickstart.md). The [AI+API page](https://sendforsign.com/docs/api-reference/mcp/aiapi) stays available for existing
integrations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.