Sigil e-signatures

com.signwithsigilPublished by signwithsigil.comOfficial publisherv1.0.7Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Sigil e-signatures: send a PDF or DOCX as a pact for signing, track signers, and fetch the signed copy.

What you can do
  • Send a PDF or DOCX document out as a pact for e-signature.
  • Track the signers and the status of a pact.
  • Fetch the signed copy once signing is complete.
When to use it
Useful when an assistant should prepare and dispatch documents for signature, follow who has signed, and retrieve the finished signed file without leaving the conversation.
Requirements
A remote endpoint at api.signwithsigil.com over streamable HTTP, with OAuth authentication. An Authorization header carrying a Sigil API key is required; keys are created in the Sigil API area and need a Pro or Business plan.
Before you install
The server needs a Sigil API key sent in the Authorization header, so treat it as a secret. Sending a pact dispatches real documents to real signers, and the documents may contain personal or confidential information.

Installation

In SourceWeft

  1. Open Sigil e-signatures in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.signwithsigil%2Fsigil/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sigil-e-signatures": {
      "type": "http",
      "url": "https://api.signwithsigil.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.7LatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.