APISign

io.apisignv1.0.0Updated Sep 28, 2026

Send documents for legally binding e-signature and manage the reusable templates behind them.

VerifiedStreamable HTTPWeb executableOther

Installation

In SourceWeft

  1. Open APISign in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apisign": {
      "type": "http",
      "url": "https://apisign.io/mcp"
    }
  }
}

README

APISign MCP Server

Send documents out for legally binding e-signature, and manage the templates they come from, directly from an AI agent.

APISign runs a hosted Model Context Protocol server at https://apisign.io/mcp. There is nothing to install and nothing to self-host — point your client at the URL, give it an API key, and your agent can draft a contract from a template, fill its variables, send it to signers, and watch the signatures come in.

This repository holds the connection metadata and client configuration. The service itself lives at apisign.io.

Connect

1. Get an API key. Sign in at apisign.io, then go to Account → API Keys and create one. Copy it — it is shown once.

Pick the permission deliberately:

PermissionWhat the agent can do
Read OnlyList and read templates and contracts. Nothing else.
Read & WriteEverything, including sending contracts, which charges your balance.

A Read Only key does not merely refuse the write tools — they are left out of the tools/list response entirely, so the agent never learns they exist. If your agent only needs to look things up, use one.

2. Add the server. The quickest route, which works for Claude, Cursor, ChatGPT and most other clients:

bash
npx add-mcp https://apisign.io/mcp --header '{"x-api-key": "your-api-key-here"}'

Or configure it by hand:

json
{  "mcpServers": {    "apisign": {      "url": "https://apisign.io/mcp",      "headers": {        "x-api-key": "your-api-key-here"      }    }  }}
ClientConfig file
Claude Desktop (macOS)~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop (Windows)%APPDATA%\Claude\claude_desktop_config.json
Cursor~/.cursor/mcp.json, or %USERPROFILE%\.cursor\mcp.json
ChatGPTSettings → Features → MCP servers → Add MCP server

Transport is Streamable HTTP. Authentication is the x-api-key header.

Tools

Twelve tools, in two families. Everything is scoped to the organization the API key belongs to.

Templates

ToolAccessWhat it does
template_listreadList all templates in the organization.
template_getreadFetch one template by ID, with its content and field definitions.
template_createwriteCreate a blank template from a name and optional Markdown.
template_updatewriteChange a template's name, content, or fields.
template_uploadwriteConvert a base64-encoded DOCX/DOC into a template.
template_archivewriteSoft-delete a template.

Contracts

ToolAccessWhat it does
contract_listreadList contracts, optionally filtered by status.
contract_getreadFetch one contract, including every signer and their status.
contract_createwriteCreate a contract from a template or from raw content, with signers.
contract_updatewriteEdit a draft contract's details or signers. Drafts only.
contract_sendwriteSend a contract for signing. Charges your balance and emails the signers.
contract_cancelwriteCancel a draft or sent contract.

Templates are Markdown with Handlebars-style variables — {{client_name}}, {{effective_date}} — that contract_create fills in. Signature placeholders work the same way: a one-signer document needs a {{signature}}, and a multi-signer document gives each party their own, assigned through signer_fields.

A worked example

Draft an NDA for Acme Corp from our standard mutual NDA template, effective the first of next month, and send it to [email protected] and to me.

The agent calls template_list to find the template, template_get to read its variables, contract_create to fill them and attach both signers, then contract_send. You get back a contract ID you can follow with contract_get.

Discovery metadata

FileConsumed by
server.jsonThe official MCP registry — published as io.apisign/apisign.
plugins/apisign/mcp.jsonCursor and other Agent Plugins clients.
glama.jsonGlama's indexer.

The server also serves its own card, without authentication, so directories can describe it without an API key:

  • https://apisign.io/.well-known/mcp.json
  • https://apisign.io/.well-known/mcp/server-card.json

Docs and support

Issues with the MCP integration are welcome here. Questions about your account belong at apisign.io.

License

MIT

Source: README.md at commit c414e9d

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026