Integration

BoloSign integration

BoloSign (the e-signature product of BoloForms) sends documents for signature. Send a PDF template or a form template to signers by email, with custom variables and mail text; list the workspace's documents with their signing status and signed PDF links; read the respondents of a PDF template and the responses of a form; remind pending signers; and void an in-progress document. Templates, forms, signer roles and webhooks are set up in the BoloSign dashboard (the public API has no route for them), and the browser embed script is not exposed. Authentication is a BoloSign API key sent in the x-api-key header; listing documents also needs the id of a workspace associated with that key.

Connect BoloSign How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in BoloSign.Built from the 6 BoloSign tools below, on the connection you add once.

What you can do with BoloSign

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 2 operations

list_documentsList documentsGETLists the workspace's documents, newest first: single signature PDFs (documentType=PDF, the default) or PDF templates (PDF_TEMPLATE), with status, signers, history and signed PDF links. Needs workspaceid. At most 100 per page.
void_documentVoid documentPOSTVoids an in-progress document. For a PDF template pass documentType PDF_TEMPLATE and responseId. A document already voided answers 200; SIGNED, PAID, DECLINED, EXPIRED or DELETED ones cannot be voided.

Form response, 1 operation

get_form_responsesGet form responsesGETReads form responses: pass formId for a paginated list, responseId for one response, or both. Each response carries its answers keyed by question label.

Reminder, 1 operation

send_reminderSend reminderPOSTEmails (or texts) a reminder to the pending signers of a document now, following its signing order. For a PDF template pass documentType PDF_TEMPLATE and responseId. Limited to 5 calls per 15 minutes per API key.

Template, 1 operation

send_template_for_signingSend template for signingPOSTSends a PDF template (signingType PDF_TEMPLATE) or a form template (FORM_TEMPLATE) to the receivers by email at once. For a PDF template, keep createdDocumentId: it is the responseId for void_document and send_reminder.

Template respondent, 1 operation

get_template_respondentsGet template respondentsGETReads the respondents (sent copies) of a PDF template: pass templateId for a paginated list, respondentDocumentId for one respondent, or both. Returns signers, their status and signing links, history and PDF URLs.

Use BoloSign from Claude Code, Cursor or Codex

Connect BoloSign in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its BoloSign operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect BoloSign

Create your workspace
Sign up free. Nothing to install.
Connect BoloSign once
Add your BoloSign connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.