MCP server

Sigil runs a Model Context Protocol server, so an AI assistant such as Claude, Cursor or VS Code's agent can work with your pacts directly. Ask it in plain language and it calls the right tools.

At a glance

What you can ask

• "Which templates do I have?"
• "Send the consulting agreement to Avery Lane and then Sam Ortiz, and copy records@example.com."
• "What is still out for signature?"
• "Has Sam signed the Acme agreement yet? Who is next?"
• "Sam never got the email. Send the link again."
• "Cancel the Acme agreement; the terms changed."
• "How many documents do I have left this month?"

How it behaves

• It acts as your account. The tools use the API key's account, with the same plan limits, glyph checks and ownership rules as the dashboard and the API, and they answer with the same JSON as the API.
• Reading is safe; changes are marked. Six tools only read. create_pact, send_pact and resend_pact make changes, and void_pact is marked destructive, so most clients ask you before running them.
• Sending costs documents. An assistant can call get_account to check the balance first. See Documents and plans.
• Signing links stay private. get_pact only includes the waiting signer's link when asked, and an assistant should only pass it to that signer.
• Templates come from the dashboard or the API. The MCP tools send saved templates; uploading a document is done on the dashboard or with Create a template.

When a client connects, the server introduces itself with these instructions:

E-signature for one account. A pact is a document out for signature: list templates, create pacts from them, send, void and check who has signed. Documents carry \s1\-style glyphs that mark the fields; recipients are numbered to match.

Keys for assistants

Give each assistant or machine its own API key, named after it (claude-desktop, cursor-laptop), so you can see when it was last used and revoke it alone. A key can do everything your account can, including sending pacts.