BoldSign MCP Server

BoldSign

BoldSign is an electronic signature platform (by Syncfusion) for sending, signing, and tracking legally binding documents. It handles the full signature lifecycle: create a signing request, route it through signers in order, track completion status, and store the signed output with an audit trail.

Core Concepts

• Signature requests (documents): The primary entity. Each request has a title, one or more files, signers with form fields (signature, date, text), and a lifecycle status. Statuses: Draft → InProgress (WaitingForMe / WaitingForOthers / NeedAttention) → Completed | Declined | Revoked | Expired.
• Templates: Reusable document blueprints with pre-configured roles, form fields, and signing order. Create a signing request from a template by filling in signer details for each role. Templates can be shared across the organization.
• Brands: Visual identity applied to signing requests — logo, colors, email display name, custom redirect URL. Each account can have multiple brands; one is marked default. Brand ID is passed when sending documents to control appearance.
• Sender identities: Verified email addresses authorized to send signing requests. Each identity is linked to a brand and must be verified before use.
• Contacts: Saved signer profiles (name, email, company, job title, phone) for quick reuse when creating signing requests.
• Teams: Organizational groupings of users for managing permissions and document visibility.
• Users: Account members with roles (admin, member) who can send/sign documents.
• Custom fields: Account-level metadata fields (scoped per brand) that can be attached to documents for categorization and reporting.

Common Workflows

1. Send from template: Enumerate templates → pick one by ID → open its full definition (roles, fields) → create a signing request by providing signer info for each role.
2. Track signing progress: Enumerate documents filtered by status (e.g. WaitingForOthers, NeedAttention) → open one document for per-signer status, form field values, and history.
3. Manage branding: Enumerate brands → open a brand’s configuration → apply that brand ID when sending documents.
4. Contact lookup: Search contacts or fetch a specific contact's details before adding them as a signer.

Gotchas

• Pagination uses 1-based page numbers (not zero-based). Default page size is 10 for most directory reads, 50 for brands.
• Document list supports nextCursor for iterating beyond 10,000 records — pass the nextCursor value from the last item in the previous page.
• Template list can be filtered by type: AllTemplates (default), MyTemplates, or SharedTemplates.
• Document statuses are compound — "InProgress" is the coarse status, but directory reads return more granular values like WaitingForMe, WaitingForOthers, NeedAttention.
• Brand ID is required to scope custom fields — enumerating custom fields without a brand returns account-level fields only.
• Sender identities must be verified (email confirmation) before they can be used to send documents.