Ignisign
IgniSign is a comprehensive electronic signature platform that enables users to sign, send, and manage documents securely online.
Verdict
Common use cases
- Send NDAs to new hires from Slack
- Check contract signing status mid-deal
- Archive signed documents after close
- Onboard signers for compliance workflows
- Cancel stale signature requests in bulk
Integration
- Vendor
- Ignisign
- Category
- other
- Auth
- API_KEY
- Tools
- 36
- Composio slug
ignisign
Tools
- Cancel Signature Request
Tool to cancel a signature request. Use after identifying the signature request to abort.
- Close Ignisign Signature Request
Tool to close an active signature request. Use when you need to end or abort a signature process.
- Create Signer
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
- Create Webhook Endpoint
Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
- Delete Documentdestructive
Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
- Delete Ignisign Signature Requestdestructive
Tool to delete a signature request. Use when you need to permanently remove a signature request by its ID.
- Delete Signerdestructive
Tool to delete a signer. Use when you need to remove a signer from a specific application environment after confirming signer ID.
- Delete Webhook Endpointdestructive
Tool to delete a specific webhook endpoint. Use when you want to remove an existing webhook by its ID.
- Get application context
Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app.
- Get Document Information
Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID.
- Get Missing Signer Inputs
Tool to determine missing inputs needed for a signer in a specific signature profile. Use after selecting a signature profile and signer to identify required fields.
- Get Signature Request Details
Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details.
- Get Signature Request Document
Tool to retrieve the document associated with a specific signature request. The action downloads the original file of a document. Provide `documentId` to select a specific document or omit to use the first available document of the request.
- Get Signature Requests
Tool to retrieve a paginated list of signature requests for an application. Use after confirming the application ID and environment.
- Get Signature Request Status
Tool to retrieve the current status of a specific signature request. Use when you need to check the state of a single request by its ID.
- Get Signed Document
Tool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fa
- Get Signer Creation Constraints
Tool to retrieve input constraints required to create a signer for a specific signature profile. Use after selecting a signature profile to determine required signer inputs.
- Get Signer Input Constraints
Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile.
- Get Signer Inputs
Tool to retrieve inputs provided by a signer for a signature request. Use after a signer has completed their input steps to fetch submitted values.
- Get Signer Profile
Tool to retrieve a signer profile. Use after obtaining the signer profile ID.
- Get Signer Profiles
Tool to retrieve signer profiles. Use when listing all profiles for a given app environment after confirming app ID and environment.
- Get Webhook Details
Tool to retrieve details of a specific webhook endpoint. Use after you have the webhook ID to inspect its URL, description, and creation timestamp.
- Get Webhooks
Tool to list all webhook endpoints configured for an application environment. Use after confirming the application ID and environment.
- Ignisign API Authentication
Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
- Initialize Document
Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
- Initialize Ignisign Signature Request
Tool to initialize a new signature request. Use when starting a signature flow in a specific application environment.
- List Documents
Tool to retrieve documents linked to a signature request. The action works by calling the signature request context endpoint and extracting its documentIds, then fetching each document detail.
- Provide Document Content Data JSON
Tool to provide JSON content for a document. Use when you need to attach or update the JSON data of a document.
- Provide Document Content File
Tool to provide file content for a document. Use after creating a document to attach its file content.
- Provide Document Content Private File
Tool to provide private content for a document via its SHA-256 hash. Use after creating a document placeholder and needing to submit the private content hash for signing.
- Publish Signature Request
Tool to publish a draft signature request. Use after adding all documents and signer details to the draft.
- Search Signers
Tool to search for signers within an application. Use after obtaining application ID and environment. Allows optional filtering by name, email, or external ID.
- Update Document Information
Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
- Update Signature Request
Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending.
- Update Signer
Tool to update details of an existing signer. Use after fetching a signer when you need to change its profile.
- Update Webhook Endpoint
Tool to update an existing webhook endpoint. Use when you have a webhook ID and want to modify its destination URL or description. Example: Update the URL of webhook `wbh_123` to `https://example.com/webhook`.
Setup
Setup guide
- 1Open your Switchy workspace settings and navigate to Integrations. Click Add MCP Server and select Ignisign from the directory. You'll be prompted to enter your Ignisign API key, which you generate from your Ignisign dashboard under API Settings. Choose the application environment you want to connect (production or sandbox). Save the configuration and return to any Space. Type '@Ignisign' in a message to confirm the connection is live. Test it by asking '@Ignisign list all signers in this environment' — you should see a response with signer data or an empty list if none exist yet. Once verified, you can create signature requests, manage signers, and monitor webhooks directly from chat.
What teammates see: by default, memories from Ignisign are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Send Contract for Signature
@Ignisign create a signature request for the Q1 vendor agreement. Add john@example.com and sarah@example.com as signers. Use the standard contract signer profile.Open in a Space →
Check Signature Status
@Ignisign show me the status of signature request ID sig_abc123. Include who has signed and who's still pending.Open in a Space →
List Active Signers
@Ignisign list all signers in the production environment. Show their email addresses and signer profile types.Open in a Space →
Delete Completed Request
@Ignisign delete signature request ID sig_xyz789. Confirm it's been completed and archived before removing.Open in a Space →
Register Webhook for Events
@Ignisign create a webhook endpoint at https://our-server.com/ignisign-events for the production app. Subscribe to signature completion and cancellation events.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Ignisign list all active signature requests for our Q1 contracts and show me which ones are still pending signatures
Based on the current signature requests in your environment, here are the active Q1 contracts: • SR-2847: Vendor Agreement - Acme Corp (2/3 signers complete, awaiting CFO signature) • SR-2851: Service Contract - Beta Industries (1/2 signers complete, awaiting client signature) • SR-2855: NDA - Gamma Partners (0/2 signers, sent 3 days ago) All three requests are within their validity period. SR-2855 has had no activity since creation and may need a follow-up.
This example shows the MCP's ability to query and synthesize signature request status across multiple documents. Requires read access to signature requests in your application environment. The actual response structure depends on your Ignisign workspace configuration and active signature workflows.
@Ignisign create a new signer for jane.doe@example.com using our standard employee profile, then initiate a signature request for the updated employee handbook
I've completed both actions: 1. Created signer: jane.doe@example.com - Signer ID: SGN-9472 - Profile: Standard Employee - Status: Active 2. Initiated signature request: Employee Handbook v2.3 - Request ID: SR-2859 - Document: handbook-2024-q1.pdf - Notification sent to jane.doe@example.com - Expiration: 14 days from now Jane will receive an email with signing instructions within the next few minutes.
This demonstrates the MCP's ability to chain operations—creating a signer and immediately using them in a signature workflow. Requires both signer creation and signature request permissions. Side-effect: sends an actual email notification to the specified address, so verify the recipient before running.
@Ignisign we need to cancel signature request SR-2843 because the contract terms changed, then delete the associated document to avoid confusion
I've processed both cleanup actions: 1. Cancelled signature request SR-2843 - Previous status: Awaiting 1 of 2 signatures - Signers notified of cancellation - Request marked as cancelled (not deleted) 2. Deleted document DOC-5621 - Filename: partnership-agreement-draft.pdf - Permanently removed from storage Note: The signature request record remains in your system for audit purposes, but the document file is permanently deleted. Any signers who had pending actions received cancellation notifications.
This example highlights the MCP's document lifecycle management capabilities and the important distinction between cancelling (audit trail preserved) versus deleting (permanent removal). Requires both signature request management and document deletion permissions. Be cautious: document deletion is irreversible and may affect compliance requirements.
Use-case deep-dives
When Ignisign fits a 5-person agency onboarding contractors
A design agency hiring 3-5 freelancers per quarter needs offer letters and NDAs signed fast. Ignisign's MCP works here because the 36 tools cover the full signature lifecycle—create signers, send requests, cancel if terms change, delete after retention expires. The API key auth means one shared credential in Switchy; no per-user OAuth dance. The webhook tools let you pipe completion events into Slack or your HRIS. Trade-off: if you're signing 50+ docs a month with complex routing (legal review, then CFO, then candidate), you'll outgrow the MCP's flat tool list and want a dedicated DocuSign integration. Below that threshold, Ignisign keeps contract ops in the same workspace as your project briefs and client comms.
Why Ignisign scales for mid-market sales teams closing 10-20 deals monthly
A 12-person SaaS sales org closing enterprise deals needs MSAs, order forms, and amendments signed without leaving their deal room. Ignisign's MCP shines because the signer-management tools let you programmatically create signers per deal, attach documents, and track status in one thread. The delete-document and delete-signer tools matter for GDPR cleanup after deal closure. Webhook endpoints push signature events into your CRM or deal Slack channel. The ceiling: if your legal team requires audit trails with tamper-evident seals or you're in a regulated vertical (finance, healthcare), Ignisign's MCP doesn't surface compliance metadata—you'll need a heavier integration. For standard B2B SaaS contracts under $100k ACV, this keeps signature ops inside your shared workspace instead of scattered across email and a separate e-sign portal.
When Ignisign handles a 3-person event team managing 15 vendor contracts per show
An event production crew books caterers, AV vendors, and venues for quarterly conferences. Each show needs 10-15 vendor agreements signed in a 6-week window. Ignisign's MCP fits because the create-signer and signature-request tools let you batch-send contracts from a shared Switchy thread, then cancel or close requests if a vendor drops out. The 36 tools cover edge cases—delete outdated templates, update webhook endpoints when your ops stack changes. The limit: if you're running 50+ events a year with overlapping vendor pools, the MCP's flat namespace gets messy (no folder or tag hierarchy). Below that scale, Ignisign keeps vendor paperwork in the same workspace as your runbook and budget tracker, so the whole crew sees signature status without switching apps.
Frequently asked
What does the Ignisign MCP do in Switchy?
The Ignisign MCP lets your team create, manage, and cancel electronic signature requests directly from Switchy's AI workspace. You can onboard signers, upload documents, track signature status, and configure webhooks for real-time notifications—all without switching to Ignisign's dashboard. It's built for teams that need to automate contract workflows through AI prompts instead of clicking through a web UI.
Do I need admin access to connect Ignisign?
You need an Ignisign API key, which typically requires admin or developer permissions in your Ignisign account. The key authenticates all 36 tools in this MCP, including creating signers, managing documents, and configuring webhooks. If you're not an admin, ask whoever controls your Ignisign account to generate the key and share it with you securely.
Can the Ignisign MCP send signature requests via email?
The MCP creates and manages signature requests in Ignisign, but Ignisign itself handles the email delivery to signers. You control the request setup (documents, signers, deadlines) through Switchy; Ignisign's platform sends the actual signature links. If you need to customise email templates or branding, configure that in Ignisign's settings before creating requests through the MCP.
How is this different from using Ignisign's web dashboard?
The MCP replaces repetitive dashboard clicks with AI-driven automation. Instead of manually uploading documents and adding signers through Ignisign's UI, you describe what you need in Switchy and the AI executes it. This matters for teams processing multiple signature requests daily—you can batch-create requests, auto-cancel expired ones, or trigger workflows based on webhook events, all from one workspace.
Who on my team should connect this integration?
Whoever manages your contract or compliance workflows and has access to your Ignisign API key. This is typically a legal ops person, contract manager, or the admin who set up Ignisign initially. Once connected in Switchy, any team member in your workspace can use the MCP to create signature requests, but the API key's permissions control what actions are allowed.