Sigil e-signatures

Official registry Productivity

Send a PDF or DOCX for e-signature as a pact, track its signers and fetch the signed copy.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http sigil-e-signatures 'https://api.signwithsigil.com/mcp' --header 'Authorization: <Bearer <your Sigil API key> (made on https://www.signwithsigil.com/api; Pro or Business plan)>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "sigil-e-signatures": {
            "type": "http",
            "url": "https://api.signwithsigil.com/mcp",
            "headers": {
                "Authorization": "<Bearer <your Sigil API key> (made on https://www.signwithsigil.com/api; Pro or Business plan)>"
            }
        }
    }
}

Frequently asked questions

What is Sigil e-signatures?

Send a PDF or DOCX for e-signature as a pact, track its signers and fetch the signed copy.

How do I install Sigil e-signatures?

It runs as a remote server. In Claude Code: claude mcp add --transport http sigil-e-signatures 'https://api.signwithsigil.com/mcp' --header 'Authorization: <Bearer <your Sigil API key> (made on https://www.signwithsigil.com/api; Pro or Business plan)>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Sigil e-signatures need an API key?

Yes. It expects Authorization, which you set in its configuration.

Who maintains Sigil e-signatures?

It is published by com.signwithsigil. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.