A

AddSign

MCP server · by rmindgh

Developer Tools npmStreamable HTTP v0.1.5

Send documents for e-signature from templates, track status, remind signers, get signed PDFs.

View source ↗ Website ↗ More servers

Install

Run one of the commands below, then add the client config underneath.

npmnpx -y addsign-mcp
Streamable HTTPhttps://addsign.io/api/mcp

Client configuration

Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.

mcpServers{
  "mcpServers": {
    "addsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "addsign-mcp"
      ]
    }
  }
}

About this server

AddSign is listed in the Developer Tools category of the MCPNav directory. It is distributed as npm, Streamable HTTP and can be loaded by any client that speaks the Model Context Protocol.

Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.

Frequently asked questions

What is the AddSign MCP server?

AddSign is an MCP server by rmindgh. Send documents for e-signature from templates, track status, remind signers, get signed PDFs.

How do I install AddSign?

Install it with: npx -y addsign-mcp. Then add the JSON config to your client's MCP settings and restart the client.

Is AddSign free to use?

The MCP server itself is free to install. The source is public on https://github.com/rmindgh/addsign-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.

Which clients support AddSign?

Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.