Lumin

Send documents for e-signature, track them, and generate agreements from templates.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Lumin connector does

The Lumin MCP server connects Lumin — a PDF and electronic signature platform — to Claude, ChatGPT and any MCP-compatible agent. Its fourteen tools send documents out for signature, track each signer, download the signed copy and certificate, and generate agreements from saved templates. Sign-in is OAuth, and the scopes genuinely separate reading from writing.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Lumin tools (14)

  • get_lumin_user_information
  • get_workspace_info
  • upload_file_to_lumin
  • lumin_markdown2pdf
  • lumin_get_templates
  • lumin_get_template_details
  • lumin_generate_document_from_template
  • send_signature_request_on_lumin
  • lumin_send_signature_request_from_template
  • get_signature_request_on_lumin_by_id
  • cancel_signature_request_on_lumin_by_id
  • lumin_get_signature_request_file
  • lumin_post_agreement
  • lumin_get_agreement_file

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Sending is irreversible in the ordinary sense. Once send_signature_request_on_lumin succeeds, the email has gone. Cancelling afterwards stops the signing but does not unsend the notification, and Lumin documents cancellation itself as irreversible.
  • One scope covers send, update and cancel. sign:requests grants all three. Consent offers no way to permit sending an agreement while withholding the ability to cancel one.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint value is published here. The parameter behaviour described above comes from Lumin's REST API reference for the endpoints the tools map onto, not from the MCP server's own schemas.
  • No reminders, no signing links, no due-date changes. Those endpoints exist in Lumin's API and in its web app, but the connector exposes none of them. An agent can start and watch a signing, not chase it.
  • No PDF operations. Merge, compress, split, password, summarise and translate are all API-only. lumin_markdown2pdf is the connector's only document-processing tool.
  • Every returned file link expires. Thirty minutes for signature request files and PDF operations, one hour for markdown-to-PDF output. Nothing the connector returns is a durable reference.
  • Plan gates bind at completion, not connection. Lumin's help centre puts monthly document limits at 10 on Starter, 30 on Pro and 200 on Business, caps uploads at 20 MB on free against 200 MB on paid, and restricts free-plan access to files older than twelve months.
  • The Certificate of Completion is not universal. Lumin states it exists only for documents sent after 12 February 2025, and that free-plan users must upgrade to Pro to retain access to it after thirty days.
  • Identity verification needs a separate licence. The verification field that demands a driver licence or photo ID returns a 403 unless Digital Trust is enabled at workspace level, which Lumin sells through an account manager.
  • We could not establish whether the MCP tools expose every REST parameter. The viewers and custom_email fields are documented on the REST endpoint the send tool maps onto; whether the tool's own schema surfaces them is not something an unauthenticated probe can tell.

Frequently asked questions

Does the Lumin connector send email to other people?

Yes, and that is its main job. Two of the fourteen tools create and send a signature request, which emails every signer you name. Lumin's own connector listing says you will always see the recipient list before it goes out. The underlying API also accepts a viewers array, so an address can receive the document without ever being asked to sign.

Can the Lumin MCP server delete my documents?

No. No tool among the fourteen carries a delete verb, and Lumin's published API reference contains no delete endpoint on any of its twenty-five paths. The nearest thing is cancelling a signature request, which Lumin documents as irreversible but which preserves the audit trail rather than removing the record.

What OAuth scopes does the Lumin MCP server request?

Thirteen, and unlike most connectors they draw a real read and write line. The server's own RFC 9728 resource descriptor advertised openid, offline_access, profile.read, settings.configure, pdf:circles.read, workspaces.read, templates.read, templates, pdf:files.read, pdf:files, sign:requests.read, sign:requests and agreements when we read it directly on 2026-08-22.

Can the connector cancel a signature request without extra permission?

Yes, and that is the sharpest edge here. Lumin's API reference assigns one scope, sign:requests, to sending a request, updating its due date and cancelling it. Granting the agent permission to send an agreement therefore also grants permission to cancel one, and Lumin's own tool description calls cancellation irreversible.

Do I need a paid Lumin plan to use the connector?

Not to connect, but the plan governs what completes. Lumin's help centre states monthly document limits of ten on Starter, thirty on Pro and two hundred on Business, and that free-plan users must upgrade to Pro to keep the Certificate of Completion after thirty days. Free accounts also cap uploads at twenty megabytes against two hundred on paid.

Where do the download links from Lumin's tools point?

At temporary signed URLs, not permanent files. Lumin documents the signature request file link as expiring after thirty minutes, the markdown-to-PDF output as valid for one hour, and every PDF operation result as temporary. To keep any of them you must download the file and upload it back to your workspace as a new document.

Can the Lumin connector send a reminder to a signer who has not signed?

Not through this connector. Lumin's REST API has a reminder endpoint, and its help centre documents reminders in the web app, but no tool among the fourteen exposes it. The same gap covers generating a signing link and changing a due date, so tracking is read-only once a request is out.

What personal data does the Lumin connector handle?

Signer identity and, on some workspaces, government ID claims. Signature request records carry each signer's name, email address and status. Lumin's Digital Trust feature lets a request demand a driver licence or photo ID and return claims including document_number and issuing_authority, though that requires a workspace licence Lumin sells separately.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Lumin to work.

Connect Lumin once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio