Signforge
Wire e-signature into your coding agent so contracts and PDFs upload, get signed, and download without leaving the terminal.
Overview
SignForge is a Build-phase MCP server that lets AI agents upload PDFs, send them for e-signature, and download signed documents via the SignForge API.
What is this MCP server?
- stdio MCP package @signforge/mcp-server v1.2.2
- Upload PDFs, send for e-signature, and download completed documents from the agent
- Requires SIGNFORGE_API_KEY from signforge.io/dashboard/developers
- Optional SIGNFORGE_API_URL for self-hosted API base URL
- Purpose-built for AI agents rather than a standalone signing UI skill
- Registry version 1.2.2
- npm package @signforge/mcp-server
- Required secret env SIGNFORGE_API_KEY
What problem does it solve?
Solo builders lose time hopping between the IDE and a signing product every time a contract or PDF needs a signature.
Who is it for?
Indie SaaS founders and agents-first workflows that routinely send NDAs, MSAs, or onboarding PDFs from the same session where code ships.
Skip if: Teams that need full CLM, in-house legal review queues, or signing without any SignForge account and API key.
What do I get? / Deliverables
After you register the stdio server with SIGNFORGE_API_KEY, your agent can run upload–sign–download steps in one conversational workflow.
- MCP tools that upload documents to SignForge
- Initiated signing requests and retrievable signed PDFs
- Agent-callable signing workflow without leaving the IDE
Recommended MCP Servers
Journey fit
Canonical shelf is Build because SignForge is an MCP integration you register in the agent to call a signing API during product and ops workflows. Integrations is the right subphase: it connects Claude Code or Cursor to SignForge’s upload–sign–download pipeline via stdio MCP and an API key.
How it compares
MCP signing integration tied to SignForge, not a generic document skill or marketplace bundle.
Common Questions / FAQ
Who is SignForge MCP for?
Solo and indie builders who use Claude Code or similar agents and want SignForge e-signature actions callable as MCP tools.
When should I use SignForge MCP?
Use it during Build (and adjacent Ship/Operate moments) when an agent should upload a PDF, request signatures, and fetch the completed file without manual tab switching.
How do I add SignForge MCP to my agent?
Install @signforge/mcp-server, configure stdio in your MCP client, set SIGNFORGE_API_KEY (and SIGNFORGE_API_URL only if self-hosted), then restart the agent.