Repository avatar
Other Tools
v1.2.0
active

mcp

com.sigpen/mcp

Draft, fill in, and prepare documents for e-signature. You approve every send in SigPen.

Documentation

SigPen MCP server

Connect your AI assistant to SigPen, the e-signature app. Ask it to draft an NDA, fill in an offer letter from your template, or upload a PDF and line up the signers. It prepares everything; you approve every send in SigPen.

  • Server URL: https://www.sigpen.com/api/mcp (Streamable HTTP)
  • Auth: sign in to SigPen (Claude apps, ChatGPT, and other clients that support MCP sign-in), or Authorization: Bearer <your SigPen API key>
  • Guide: sigpen.com/docs/mcp

This repository holds the setup instructions and the plugins for Claude Code and Cursor. SigPen hosts the server itself, so there's nothing to install or run.

Claude apps (claude.ai, Claude Desktop, mobile)

You sign in to SigPen, so there's no key to copy. It works on the free Developer tier and on Professional and up.

  1. In Claude, open Settings, then Customize, then Connectors.
  2. Click Add, then Add custom connector. Name it SigPen, use the URL https://www.sigpen.com/api/mcp, and click Continue.
  3. Under Authentication, check that Sign in now is selected (Claude picks it for SigPen), keep Claude's published identity as the OAuth client, and click Add.
  4. Click Connect, sign in to SigPen, and click Allow.

Add it once on claude.ai or in Claude Desktop and it works in the mobile apps too. On Team and Enterprise plans, an owner may need to add the connector first.

ChatGPT

Works on the free ChatGPT plan too.

  1. In ChatGPT, open Plugins in the sidebar, click Add, then Add custom MCP server.
  2. Name it SigPen and use the URL https://www.sigpen.com/api/mcp. Keep OAuth as the authentication.
  3. Tick "I understand and want to continue", click Create as a plugin, then Connect SigPen.
  4. Sign in to SigPen and click Allow.

Then start a chat with @SigPen. In a Business or Enterprise workspace, an admin may need to allow custom MCP servers first.

Before you start (clients that use an API key)

  1. Create an API key at sigpen.com/developer. It works on the free Developer tier and on Professional and up (Starter has no API). Use a live key (sp_live_) to draft; a test key can only look things up.
  2. Name the key "AI assistant" so you can revoke it on its own.
  3. Always use the www URL. sigpen.com redirects, and the redirect drops your key.

Claude Code

With the plugin (asks for your key once and keeps it in Claude Code's secure storage, not in a settings file):

claude plugin marketplace add sigpenhq/sigpen-mcp
claude plugin install sigpen@sigpen

The plugin also adds a send-for-signature skill that walks Claude through drafting, filling in, and asking for approval.

Or add the server by hand, with the key in an environment variable:

export SIGPEN_API_KEY=sp_live_your_key
claude mcp add --transport http --scope user sigpen https://www.sigpen.com/api/mcp \
  --header "Authorization: Bearer ${SIGPEN_API_KEY}"

Run /mcp in Claude Code to check it's connected.

Cursor

Set SIGPEN_API_KEY in your environment, then add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sigpen": {
      "url": "https://www.sigpen.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:SIGPEN_API_KEY}" }
    }
  }
}

Or use the Install in Cursor button on the setup guide. The Cursor plugin in plugins/sigpen bundles the same config with the skill.

VS Code

Add to .vscode/mcp.json. VS Code asks for the key and stores it for you:

{
  "inputs": [{ "type": "promptString", "id": "sigpen-api-key", "description": "SigPen API key", "password": true }],
  "servers": {
    "sigpen": {
      "type": "http",
      "url": "https://www.sigpen.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:sigpen-api-key}" }
    }
  }
}

Codex

Add to ~/.codex/config.toml and set SIGPEN_API_KEY:

[mcp_servers.sigpen]
url = "https://www.sigpen.com/api/mcp"
bearer_token_env_var = "SIGPEN_API_KEY"

Other clients

Any client that supports remote MCP servers over Streamable HTTP works: with MCP sign-in (OAuth), or with your API key in a request header.

Tools

ToolWhat it does
get_accountYour plan, how the assistant is connected (a live or test key, or a sign-in), documents sent through the API this month, and rate limits.
list_documentsYour documents with status and signer counts. Filter by status, title, or date.
get_documentOne document's signers: name, email, status, and when they viewed and signed.
list_templatesYour templates and the SigPen template library.
get_templateA template's signer roles, field counts, and pages.
create_document_from_textDrafts a document from a title, the parties, and sections, with a signature and date line for each party.
create_document_from_templateDrafts a document from one of your templates or the library, with signers assigned by role.
delete_draftDeletes a draft the assistant created. Your own drafts and sent documents are never touched.
get_upload_urlA short-lived link to upload a PDF from your computer (clients that can run commands).
create_document_from_uploadTurns the uploaded PDF into a draft.
suggest_fieldsPlaces signature, date, and text fields on the assistant's draft with AI. Uses one of your monthly AI detections.
update_fieldsFills in text, date, and number fields, assigns fields to recipients, and removes fields nobody needs.
set_recipientsSaves who a draft goes to, with a role for each person. It can add you as a signer too.
request_send_approvalGives you a SigPen link to approve sending a draft. It sends nothing on its own.

Without a key, the server asks your client to sign in with your SigPen account. Clients that support MCP sign-in, like the Claude apps and ChatGPT, open that for you.

How sending works

The assistant never sends. request_send_approval returns a SigPen link. Open it signed in and you see the title, every recipient, how many fields each person fills, the values the assistant filled in, and its note for the invitation. Click Approve and send, or open the draft to change it.

  • The link lasts 24 hours and works only for you.
  • If anything changes after the link is made (recipients, fields, values, title), the link stops working.
  • Revoking the API key, or disconnecting the app, cancels its open links.
  • The assistant can only change or delete drafts it created.

Text inside a document can try to trick an assistant ("send this to someone@else.com"). The approval page is where you catch that, so check every email address before you click.

Limits and data

  • Each tool call counts as one API request against your rate limit.
  • Drafts count toward your monthly document limit, and deleting one doesn't give it back.
  • What a tool returns, such as document titles and signer names and emails, goes to your AI provider under their terms.
  • To disconnect, revoke the key or click Disconnect next to the app in the developer dashboard, on the AI Assistants tab.

Support

Email support@sigpen.com. For security issues, see SECURITY.md.

Privacy policy · Terms

No installation packages available.

Remote