MCP Connector

Give Claude access
to your LexoSign account.

Send documents for signature, check who still needs to sign, manage templates, and run PDF tools — all from a conversation with Claude. You choose what Claude can see and do, and you can revoke access at any time.

OAuth 2.1 + mandatory PKCE 19 tools Streamable HTTP transport Scoped & revocable access
What this connector does

Your LexoSign account, reachable from a conversation.

The LexoSign MCP connector is a bridge between Claude and your LexoSign account. Once connected, Claude can call the same document, envelope, template, and PDF-tool operations available on lexosign.com — nothing more. It cannot see your password, and it only ever acts within the permissions you approve.

Setup

How to connect.

Takes under a minute. You'll authenticate with your normal LexoSign login — Claude never sees your credentials directly.

  1. Open Claude's connector settings

    In Claude, go to Settings → Connectors. If LexoSign appears in the directory, add it directly; otherwise choose Add custom connector.

  2. Point it at LexoSign

    Enter the connector URL: https://mcp.lexosign.com

  3. Sign in and approve access

    You'll be redirected to LexoSign's own sign-in page (not Claude's), then shown exactly which permissions are being requested — read your documents, send envelopes, run PDF tools, and so on. Approve only what you're comfortable with.

  4. Start a conversation

    Ask Claude things like "who still needs to sign the vendor agreement I sent last week?" or "send the NDA template to jane@acme.com." Claude will call the relevant tool and show you what it did before anything is sent.

Capabilities

19 tools, grouped by what they're allowed to do.

Read-only tools run without a confirmation prompt. Tools that create, change, or delete anything always ask you to confirm first — Claude cannot silently send a document or delete a template.

Read-only

no confirmation needed
list_documentsList your documents, filterable by status and date
get_documentMetadata and status for one document
list_envelopesSignature envelopes with signer counts
get_envelope_statusSigner-by-signer status for one envelope
list_templatesYour reusable document templates
get_templateA template's fields and signer roles
get_account_usagePlan tier, monthly sends used, seat count
download_signed_documentThe completed, signed PDF
download_documentThe current PDF at any stage — signed once complete, otherwise the working document

Write

confirm before running
create_envelopeSend a document for signature
send_from_templateSend a saved template to named signers
send_reminderNudge one signer who hasn't completed yet
bulk_remind_signersNudge every pending signer across several envelopes at once
create_templateSave a document as a reusable template
apply_pdf_toolMerge, split, compress, or convert a PDF
bulk_void_envelopesCancel several pending envelopes at once

Destructive

always confirmed, idempotent
void_envelopeCancel a pending signature request
delete_documentPermanently delete a document
delete_templatePermanently delete a template
Permissions

Scoped access, nothing implied.

Every tool maps to exactly one OAuth scope. Granting read access never implies write access, and no scope grants void or delete rights beyond its own resource.

  • ✓ Access tokens are short-lived and refresh tokens rotate on every use
  • ✓ Revoke access anytime from Integrations in your LexoSign account — no email or support ticket needed
  • ✓ The same subscription-tier and email-verification checks that apply on lexosign.com apply here too — a Free-tier token can't send an envelope just because it asked
  • ✓ Every action taken through the connector is written to the same audit trail as actions taken on the website
OAuth scopes
documents:readView documents & status
envelopes:readView envelopes & signer status
templates:readView templates
account:readView plan, usage, seats
envelopes:writeSend envelopes & reminders
templates:writeSave documents as templates
pdf:toolsMerge, split, compress, convert
envelopes:voidCancel pending requests
documents:deletePermanently delete documents
templates:deletePermanently delete templates
Data handling

What crosses the wire, and what doesn't.

When a tool runs, LexoSign returns only the data that tool asks for — a document's metadata, a signed PDF's bytes, a template's field list — to Claude for that one exchange. LexoSign does not receive or store anything about your conversation with Claude beyond the tool call itself, and Claude does not receive your LexoSign password or any data outside the scopes you approved. Full detail is in the Privacy Policy, under "MCP Connector & AI Agent Access."

Questions

Need help connecting?

Reach out and we'll walk you through it, or read the privacy policy for the full data-handling detail.

Contact us Manage connected apps