Signforge MCP Server

SignForge MCP Server — Send documents for e-signature from Claude Desktop, Claude Code, Cursor, and other AI agents

Remote serverstreamable-http

What is the Signforge MCP MCP server?

If you already use Signforge MCP, the signforge mcp mcp server is the piece that lets your assistant work with it directly. SignForge MCP Server — Send documents for e-signature from Claude Desktop, Claude Code, Cursor, and other AI agents.

What the server does

  • Send documents for signature — — upload a PDF, specify a signer, and send in one step
  • Manage envelopes — — send, void, delete, and check status
  • Download documents — — signed PDFs, audit certificates, and ZIP archives
  • Use templates — — create envelopes from reusable templates with pre-filled fields
  • Manage webhooks — — subscribe to real-time envelope events
  • Generate embed URLs — — create embeddable signing experiences

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — The Cursor tool exposed by this server
  • Templates — The Templates tool exposed by this server
  • Webhooks — The Webhooks tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: SIGNFORGE_API_KEY, SIGNFORGE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Signforge MCP's toolset — Cursor, Templates, Webhooks — is a fair guide to whether it matches your workflow. It is maintained by kumarprobeops; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Signforge MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
TemplatesThe Templates tool exposed by this server.
WebhooksThe Webhooks tool exposed by this server.

How to install the Signforge MCP MCP server

{
  "mcpServers": {
    "signforge": {
      "command": "npx",
      "args": ["-y", "@signforge/mcp-server"],
      "env": {
        "SIGNFORGE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SIGNFORGE_API_KEYCredential the server authenticates with.Yes
SIGNFORGE_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Signforge MCP to Cursor.
  • Use Signforge MCP to Templates.
  • Use Signforge MCP to Webhooks.

Frequently asked questions

It connects Signforge MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Cursor, Templates, Webhooks) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Signforge MCP directly.