← All integrations

Ignisign MCP server

42 operations0 webhooks

Electronic signature and document workflow integration for Ignisign eIDAS-compliant digital signatures.

Try Ignisign with your agent

Connect Ignisign, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Ignisign on my account, then run one read-only example and show me the result.

Runs once, when you ask

Ignisign tools and triggers

Tools are what your agent can do in Ignisign through Corsair's MCP server. Triggers are the Ignisign events a routine can start from.

Documents

  • Check AuthenticityRead-only

    Check that a file (base64) is the one that was signed for a document

    documents.checkAuthenticity

  • Download Original DocRead-only

    Download original document file as binary data

    documents.downloadOriginalDoc

  • GetRead-only

    Get document record and metadata by ID

    documents.get

  • Get ContextRead-only

    Get document context including signature summaries and statements

    documents.getContext

  • InitializeWrite

    Initialize a document descriptor for a signature request

    documents.initialize

  • Provide File ContentWrite

    Upload the file or PDF content of a document (base64, sent as multipart)

    documents.provideFileContent

  • Provide Json ContentWrite

    Provide structured JSON data content for a document

    documents.provideJsonContent

  • Provide Private ContentWrite

    Provide SHA-256 document hash for private client-side managed documents

    documents.providePrivateContent

  • RemoveDestructive

    Delete a document and its associated records

    documents.remove

  • Remove ContentDestructive

    Remove document content while preserving the document descriptor

    documents.removeContent

  • UpdateWrite

    Update document metadata and display template settings

    documents.update

Signature Requests

  • CloseDestructive

    Close a signature request; signers can no longer sign it (cannot be undone)

    signatureRequests.close

Connect Ignisign to Claude, ChatGPT or Cursor

  1. 1

    Connect Ignisign in Corsair

    Add your Ignisign API key once in Corsair. Corsair stores the credential encrypted and makes the Ignisign API calls for your agent, so it never goes into a prompt or a config file. Connect Ignisign

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Ignisign. On a ChatGPT personal plan, connect Ignisign here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Ignisign's read and write operations run right away and its 8 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/ignisign, add the Ignisign plugin, and connect with an API key. Then call methods like corsair.ignisign.api.applications.getContext() from your app. Corsair keeps each tenant isolated.

Yes. Ignisign requires an API key from your Ignisign account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Ignisign, GitHub, Notion, Stripe, and the rest. Trigger Ignisign from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for electronic signature and document workflow integration for Ignisign eIDAS-compliant digital signatures. Common builds include sync jobs, admin tooling, and agents that call Ignisign APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Ignisign API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/ignisign in the open repo. When Ignisign ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Ignisign data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Ignisign data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Ignisign on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 8 destructive Ignisign operations. You can change a link's mode at hub.corsair.dev/me.