SignWell
Unclaimed verified 3 oct 2026Simple, affordable electronic signatures for businesses.
TL;DR
SignWell is a lightweight e-signature and document-workflow platform for freelancers, small businesses, professional-services firms, and software companies that need an API. Its key differentiator is the combination of a simple signing experience, relatively transparent pricing, unlimited documents on paid plans, and embedded-signing capabilities without the heavier enterprise overhead of larger competitors.
What Users Actually Pay
No user-reported pricing yet.
Our Take
SignWell occupies the value-oriented segment of the electronic-signature market. It covers the core workflow most small organizations need: preparing documents, assigning signing fields, sending requests, tracking completion, issuing reminders, and maintaining audit records. Its interface and recipient experience are designed to minimize training and friction. The product's strongest advantages are ease of use, affordability, and a practical feature set. External reviews commonly praise the clean interface, quick setup, responsive customer support, and price-to-value ratio. Paid plans that avoid strict per-document limits can be attractive to consultants, agencies, recruiters, accountants, and other businesses that send recurring agreements. SignWell is also more relevant to software teams than a basic manual-signature product because it offers API and embedded-signing functionality, webhooks, templates, and workflow controls. However, it is not necessarily the best choice for organizations seeking a broad contract-lifecycle-management suite, advanced document authoring, extensive enterprise integrations, or highly specialized identity-verification workflows. The product is best suited to small and midsize organizations that want reliable electronic signatures without the complexity or cost of a large enterprise platform. Buyers should evaluate mobile usability, field customization, in-app document editing, integration depth, and enterprise administration requirements before selecting it.
Alternatives
Ranked by Revuo score — paid tiers never affect order.QuickBooks
Smart Tools. Better Business.
Mercury
Radically different banking for startups and scaling companies
sevdesk
All-in-one digital accounting software for freelancers and small businesses in Germany
Lexware Office
Cloud accounting software for self-employed professionals and small businesses
easybill
Das Rechnungsprogramm für jede Branche – einfach & professionell
Sage
Helping business flow with accounting, ERP, payroll and HR software for SMBs
Pros
- + Generally easy to learn and quick to deploy for both senders and recipients.
- + Competitive pricing and a free tier make it accessible to freelancers and small businesses.
- + Paid plans provide unlimited or high-volume document sending relative to many per-envelope competitors.
- + API, embedded signing, webhooks, templates, and workflow features support software and automation use cases.
- + Reviews commonly describe customer support as responsive and helpful.
Cons
- - The free plan's monthly document limit may be restrictive for regular business use or extended evaluation.
- - In-platform editing of uploaded documents may be limited compared with broader document-management platforms.
- - Some reviewers report that mobile signing or document review is less convenient than the desktop experience.
- - Field customization and advanced workflow configuration may not be as extensive as in larger competitors.
- - Some anecdotal reviews mention occasional email-delivery or recipient-completion friction.
MCP Integrations
3 servers18 tools4,088 total usesManage business data including invoices, companies, and contacts through a structured database interface. Discover available data schemas to efficiently query specific records for reporting and dashboarding. Streamline administrative tasks by creating new company profiles and personnel entries directly.
4 tools
well_get_schemaDiscover available data types and fields. USAGE: - well_get_schema() → List available roots (invoices, companies, people, documents, connectors) - well_get_schema({ root: "invoices" }) → List all available fields for invoices WORKFLOW: 1. Call well_get_schema(root) to see available fields 2. Pick the fields you need for your task (typically 5-15) 3. Call well_query_records with those specific fields Returns field paths like: - "invoices.grand_total" → scalar field - "invoices.issuer.name" → relationship field (company name) - "invoices.receiver.name" → relationship field To use in well_query_records, convert path to array: "invoices.issuer.name" → ["invoices", "issuer", "name"]well_query_recordsQuery records from Well's database. ⚠️ WORKFLOW: 1. Call well_get_schema(root) FIRST to discover available fields 2. Select ONLY the fields you need (5-15 typically) 3. Call well_query_records with those specific fields ROOTS: invoices, companies, people, documents, connectors EXAMPLE - Get all invoices for dashboard: well_query_records({ root: "invoices", fields: [ ["invoices", "invoice_number"], ["invoices", "grand_total"], ["invoices", "issue_date"], ["invoices", "issuer", "name"], ["invoices", "receiver", "name"] ], limit: 500 }) ⚠️ RULES: - ALWAYS select specific fields (not allFields) for best performance - Field paths from schema: "invoices.issuer.name" → ["invoices", "issuer", "name"] - With specific fields, you can request up to 500 records Returns { rows, totalCount, success }.well_create_companyCreate a new company in Well. ⚠️ Call well_get_schema("companies") FIRST to discover all available fields and their required status. REQUIRED: name COMMON FIELDS: domain, description, tax_id, registered_name, trade_name The schema may include additional fields - use get_schema to see the complete list.well_create_personCreate a new person/contact in Well. REQUIRED: first_name (last_name can be null) FIELDS: first_name, last_name, email, phone, job_title EXAMPLES: - Simple: well_create_person({ first_name: "John", last_name: "Doe" }) - With email: well_create_person({ first_name: "John", last_name: "Doe", email: "[email protected]" }) - Full: well_create_person({ first_name: "John", last_name: "Doe", email: "[email protected]", phone: "+33612345678", job_title: "CEO" })
Model Context Protocol server that orchestrates SignWell's e-signature workflows — create, send, track, and manage documents and templates.
14 tools
file_storeStore a user's existing file for upcoming SignWell requests. Returns a file_token you can pass to document/template tools. IMPORTANT: This tool is for the USER'S EXISTING FILES only. Do NOT read, parse, or convert the file — upload it as-is. HOW TO PROVIDE THE FILE (in order of preference): 1. No arguments — Opens a native OS file picker dialog. USE THIS BY DEFAULT. Simply call file_store with no arguments and the user will select the file themselves. 2. file_path — Only if the user explicitly provides a local path on their computer (e.g. ~/Documents/contract.docx). 3. file_url — A publicly accessible URL to the file. CHAT ATTACHMENTS: When a user uploads/attaches a file in the chat, DO NOT use resource_uri — those are sandboxed and inaccessible. Instead, call file_store with NO arguments to open the native file picker. CLAUDE-GENERATED FILES: If YOU created the file content (e.g. generated a PDF), do NOT use file_store. Pass file_base64 directly to document_create instead.file_validate_text_tagsValidate text tags in a PDF before creating a template or document. RECOMMENDED WORKFLOW: file_store → file_validate_text_tags → template_create/document_create Accepts a PDF via file_token (from file_store), file_base64, file_url, or resource_uri. Set use_picker: true to open a native file picker when no file input is provided. Extracts text from the PDF and checks for valid SignWell text tags like {{signature:1:y}}. Returns: - Whether text is extractable from the PDF - List of valid tags found - List of malformed tags (if any) - Signer numbers referenced - Recommendations for fixing issuesdocument_createCreate a SignWell document (always created as a draft). CRITICAL RULES: - Do NOT read, parse, extract, or verify file contents before uploading. The user already knows what is in the file. - Do NOT convert files between formats (e.g. do NOT convert .docx to .pdf). SignWell handles conversion automatically. - The user will place signature fields in the SignWell editor. Just upload the file and return the editor link. SUPPORTED FILE TYPES: .pdf, .doc, .docx, .pages, .ppt, .pptx, .key, .xls, .xlsx, .numbers, .jpg, .jpeg, .png, .tiff, .tif, .webp, .html, .htm WORKFLOW FOR USER'S EXISTING FILES: 1. file_store (call with NO arguments to open native file picker) → returns file_token 2. document_create (pass file_token in files array) → creates draft, returns editor_url WORKFLOW FOR CLAUDE-GENERATED FILES: 1. document_create with content_text directly (RECOMMENDED) → MCP server converts to DOCX automatically Pass plain text or Markdown as content_text. The server generates a DOCX file without base64 overhead. 2. document_create with file_base64 directly (skip file_store) → creates draft, returns editor_url Do NOT write the file to disk and pass a file_path — sandbox paths are inaccessible. Use file_base64. Example using content_text: { "name": "Service Agreement", "recipients": [{"id": "1", "email": "[email protected]"}], "files": [{"name": "agreement.docx", "content_text": "# Service Agreement\n\nThis agreement between..."}] } FILE ACCESS: Chat attachments and sandbox paths (/home/claude, /mnt/user-data) are inaccessible to the MCP server. Do NOT use resource_uri or sandbox file_path values. For existing files, call file_store with no arguments to open the native file picker. REQUIRED PARAMETERS: 1. name: Document name 2. recipients: Array with at least one object containing "id" and "email" 3. files: Array with at least one file object containing: - "name": Filename (e.g., "contract.docx") - One content source (in order of preference): * "content_text": Plain text or Markdown to auto-convert to DOCX (RECOMMENDED for Claude-generated content) * "file_token": Token from file_store (recommended for user files) * "file_url": Public URL to the file * "file_base64": Base64-encoded file content * "resource_uri": MCP resource URI EXAMPLE (docx via file_token — most common): { "name": "NDA Agreement", "recipients": [{"id": "1", "email": "[email protected]"}], "files": [{"name": "nda.docx", "file_token": "<token from file_store>"}] } EXAMPLE (pdf with text tags): { "name": "Contract", "text_tags": true, "recipients": [{"id": "1", "email": "[email protected]"}], "files": [{"name": "contract.pdf", "file_token": "<token from file_store>"}] } TEXT TAGS (optional): Set text_tags: true only if the document already contains signature placeholders like {{signature:1:y}}. The recipient "id" MUST match the number in text tags (id:"1" matches {{signature:1:y}}).document_listList SignWell documents with optional filtering (status, archived, search).document_getFetch the latest status for a SignWell document.document_send_draftSend a previously created draft document (requires confirm_send).document_send_reminderSend a reminder email for a document (optionally to a specific recipient).document_completed_pdfFetch the completed PDF. Use mode: 'base64' to get content for displaying in an artifact or chat (embed as data:application/pdf;base64,{pdf_base64}). Default 'url' mode returns a shareable link.template_createCreate a SignWell template for reusable signature documents. RECOMMENDED WORKFLOW: 1. file_store (provide file_path, file_url, or resource_uri) → returns file_token 2. file_validate_text_tags (pass file_token) → validates tags are extractable 3. template_create (pass file_token in files array) → creates the template REQUIRED PARAMETERS (both are mandatory): - files: Array with at least one file object containing: * "name": Filename (e.g., "template.docx") * One content source (in order of preference): - "content_text": Plain text/Markdown to auto-convert to DOCX (RECOMMENDED for generated content) - "file_token": Token from file_store (recommended for uploaded files) - "file_base64": Base64-encoded file content - "file_url": Public URL to the file - "resource_uri": MCP resource URI - placeholders: Array with at least one placeholder object containing "id" and "name" STEP-BY-STEP EXAMPLE (using file_token): 1. Call file_store with {"file_path": "/path/to/doc.pdf"} → get file_token 2. Call file_validate_text_tags with {"file_token": "..."} → confirm tags are valid 3. Call this tool with: { "name": "My Template", "files": [{"name": "doc.pdf", "file_token": "<token from file_store>"}], "placeholders": [{"id": "1", "name": "Signer"}], "text_tags": true } ALTERNATIVE (inline base64): { "name": "My Template", "files": [{"name": "doc.pdf", "file_base64": "JVBERi0xLjQK..."}], "placeholders": [{"id": "1", "name": "Signer"}], "text_tags": true } TEXT TAGS (when text_tags: true): Your PDF must contain these literal text strings as SELECTABLE TEXT (not images): - {{signature:1:y}} - Signature field for placeholder id "1" - {{date:1:y}} - Date field for placeholder id "1" - {{text:1:y:Label}} - Text field with label - {{initial:1:y}} - Initials field The number in the tag (1, 2, etc.) MUST match a placeholder "id" in your request. CRITICAL: Text tags must be SELECTABLE/SEARCHABLE text in the PDF, not rendered as images or graphics. When generating PDFs programmatically, use text drawing methods (e.g., drawString) with standard fonts. To verify: open the PDF and try to select/copy the tag text with your mouse. If you can't select it, SignWell can't parse it. MULTI-SIGNER EXAMPLE: { "name": "Contract", "files": [{"name": "contract.pdf", "file_base64": "JVBERi0xLjQK...actual base64 here..."}], "placeholders": [ {"id": "1", "name": "Client"}, {"id": "2", "name": "Vendor"} ], "text_tags": true } For this example, the PDF should contain: {{signature:1:y}} for Client and {{signature:2:y}} for Vendor. COMMON ERRORS: - Empty arguments {} = You forgot to include files and placeholders arrays - "fields": [] in response = PDF doesn't contain valid text tags, or text_tags wasn't set to truetemplate_updateUpdate an existing SignWell template. Only provide fields you want to change.template_getFetch an individual SignWell template by ID.template_listList SignWell templates with pagination.template_deleteDelete a SignWell template.template_create_documentCreate and send a document from a template. Templates are pre-configured and ready to send, so this tool sends the document for signing by default. IMPORTANT: When a user asks to "send a template" or "send a document from a template", the document will be sent immediately for signing. Set draft: true ONLY if the user explicitly asks to create a draft or review before sending. REQUIRED: - template_id: The template ID to create the document from - recipients: Array of recipient objects, each with: - id: Unique identifier for this recipient (e.g., "recipient_1") - placeholder_name: Name of the template placeholder to assign (must match exactly) - email: Recipient's email address - name: (optional) Recipient's display name Example: { "template_id": "abc123", "recipients": [{ "id": "recipient_1", "placeholder_name": "Client", "email": "[email protected]", "name": "John Doe" }] }
Needs a self-provisionable API key
Send documents for e-signature, track signing, and manage templates in SignWell from any MCP client.
Last checked Oct 4, 2026
[ features ]
Geostrategic Position
Information on which part of the world this product / vendor belongs to, i.e. the country of their headquarters primarily, but also their hosting options etc.
Find which geostrategic world region the headquarter is located in. Relevant for compliance questions (e.g., CLOUD Act) or risk of cut-off in case of conflicts. For example, some EU companies are worried about the US and would definitely not host their customer with Chinese or Russian companies.
The hosting provider that is used to host this product, if any.
Compliance & Security
Security certifications, compliance features, and access control capabilities.
SOC 2 Type I or Type II certification.
ISO 27001 information security certification.
Complete audit log of all data changes.
Granular permissions based on user roles.
Developer Experience
Tools and abstractions easing agent development and iteration.
No-code/low-code UI for designing agent workflows.
OpenAI API-compatible endpoints or SDKs.
Available as open-source with community contributions.
Programming languages with official SDK support.
Ready-to-use, customizable UI elements for auth flows.
Self-service admin dashboard for customers to manage users/orgs.
Pricing & Plans
Pricing structure, tiers, and value propositions.
Offers a usable free plan or tier.
One-time payment for perpetual access.
Use existing servers/infra without lock-in.
No limits on number of sites/apps/projects.
Availability of a free plan or trial with usable outputs.
Entry-level price for basic generation package.
Whether usage is limited by credits rather than unlimited in plans.
Discounted or bulk options for teams/enterprises.
Offers a permanent free plan with usable limits
Invoicing & Billing
Core invoicing features including automation, templates, and payment handling
Can generate and process XRechnung e-invoices (the German EN 16931 CIUS required for B2G and the B2B e-invoicing mandate).
Supports the ZUGFeRD hybrid e-invoice format (PDF/A-3 with embedded EN 16931 XML), including Factur-X profiles.
Supports the Peppol BIS Billing format and exchange of e-invoices via the Peppol network.
Supports automatic generation and sending of recurring invoices
Automated payment reminders and dunning processes
One-click conversion from quotes/offers to invoices
Includes GiroCode or EPC QR codes for easy bank transfers
Accounting Integrations
Connections to banking, tax systems, and export formats
Supports direct export to DATEV accounting software
Automatic matching of bank transactions with bookkeeping
Direct connection for VAT pre-registration and tax filings
Receipt & Document Management
Features for capturing, digitizing, and organizing receipts and documents
AI-powered OCR for scanning and extracting receipt data
Mobile app with camera-based receipt upload and processing
Automatically suggests accounts and categories for receipts
Compare With
Reviews
No reviews yet. Be the first to review SignWell!