Draft, fill in, and prepare documents for e-signature. You approve every send in SigPen.
Connect Remote server
claude mcp add --transport http mcp https://www.sigpen.com/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"mcp": {
"url": "https://www.sigpen.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "http",
"url": "https://www.sigpen.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://www.sigpen.com/api/mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. A SigPen API key, sent as a Bearer token. Without it, your client signs in to SigPen. |
Details
| Endpoint | https://www.sigpen.com/api/mcp (Streamable HTTP) |
| First published | 15 Nov 2026 |
| Last updated | 15 Nov 2026 |
| Registry name | com.sigpen/mcp |
More files and documents servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.