APISign MCP MCP server

An official MCP server by APISign that allows AI agents to programmatically manage e-signature templates and send legally binding contracts. It supports creating, updating, and archiving templates, as well as listing, creating, and retrieving contract details with signer information. The server uses Streamable HTTP transport and requires an API key for authentication, integrating seamlessly with clients like Claude Desktop and Cursor.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

API keyEndpoint checked 2026-10-05Operated by APISign

MCP endpoint (Streamable HTTP)

https://apisign.io/mcp

Vendor documentation

What you can do with it

List all organization templates
Create a new contract from a template
Get contract details and signer status
Upload DOCX files to create templates

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http apisign-mcp https://apisign.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add apisign-mcp --url https://apisign.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable apisign-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "apisign-mcp": {
      "url": "https://apisign.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "apisign-mcp": {
      "type": "streamableHttp",
      "url": "https://apisign.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start apisign-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http apisign-mcp https://apisign.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "apisign-mcp": {
      "url": "https://apisign.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "apisign-mcp": {
      "serverUrl": "https://apisign.io/mcp"
    }
  }
}

See all 1,687

Do you run APISign MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing