Claude Lumin connectorWhat Claude can do in your Lumin account.
The Claude Lumin connector exposes 14 tools. 7 read your profile, workspace, templates and signature requests, 7 create documents, send or cancel requests, and none is left undescribed. It is the remote one: Lumin also lists a separate desktop extension with 7 tools.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Lumin into Claude
Lumin describes this connector as a signature desk inside the conversation. You hand Claude a PDF or name a saved template, it prepares the signature request, and later tells you who has signed and fetches the finished copy. The directory lists two Lumin entries from the same publisher: this remote connector with 14 tools, and a desktop extension with 7 that cannot use templates.
An NDA out for signature in one request. send_signature_request_on_lumin sends a request from a file, and lumin_send_signature_request_from_template does it straight from a saved template. Lumin's own example: an NDA to two people, due in 14 days.
A status check that ends with the signed file. get_signature_request_on_lumin_by_id shows each signer's status, then lumin_get_signature_request_file fetches the signed agreement, the Certificate of Completion or a merged copy.
A proposal built from your template. lumin_get_template_details reveals a template's fields and variables, and lumin_post_agreement fills an AgreementGen agreement with your data.
What it does not do: the sheet carries no tool that edits a document already sent, and a cancelled request cannot be restarted. It also never sends a reminder on its own or reacts when a signer finishes; Claude acts only while it answers you. For that kind of follow-up, the Lumin Make integration runs scenarios in the background.
Five words before you connect
The vocabulary of Claude connectors, explained once.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector hands to Claude. Claude chooses which ones to call as it answers, and the directory sheet lists every one.
- Authorization
- Lumin's own sign-in screen, where you grant the access Claude will use afterwards. It is given once per person and can be taken back.
- Approval
- The confirmation Claude waits for before it changes something in your account, shown in the conversation when it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Lumin.
Connect the Claude Lumin connector in three steps
- 01
Find the right Lumin entry
In Claude's settings, open Customize, then Connectors, and pick the Lumin connector that works on Claude itself, not the desktop extension. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first.
- 02
Start the connection
Click Connect on its line. Lumin opens its own sign-in window: log in with the Lumin account whose documents and templates Claude should use, since the connector needs one.
- 03
Review the permission screen
Lumin then shows what the access covers. That screen is Lumin's, not Claude's, and it sets what Claude can reach. Approve it, and use Disconnect later to cut the link.
The 14 tools of the Lumin connector
Lumin gives Claude 14 tools: 7 that read your account, 7 that change something in it.
Lumin describes each of these tools in its developer documentation, so every one sits on a clear side. Names stay exactly as Claude shows them.
- 7 read
- 7 write
What Claude reads (7)
7 toolsYour profile, workspace, templates, signature request status and the files you can download.
get_lumin_user_information
Returns the profile of the signed-in Lumin user: ID, name and email. Claude uses it to know whose account it is working in.
get_workspace_info
Gives the details of your current workspace, including its name, owner, member count and number of Spaces.
lumin_get_templates
Lists every template available in your current workspace, the starting point for anything Claude later builds from one of them.
lumin_get_template_details
Opens one template and returns its signer roles, fields, tags and variables. Lumin suggests inspecting them first, and Claude reads them to know what it has to fill in.
get_signature_request_on_lumin_by_id
Retrieves one signature request by its ID, with its status, its signers and its expiration date.
lumin_get_signature_request_file
Gets a temporary download link for the file of a completed signature request: the signed agreement, the Certificate of Completion, or a merged copy of both.
lumin_get_agreement_file
Hands back a temporary download link for the PDF of an agreement created with AgreementGen.
What Claude creates, sends or cancels (7)
7 toolsUploads, PDFs, generated documents and agreements, signature requests sent or cancelled. Lumin describes a recipient preview for sending; otherwise the general rule applies.
upload_file_to_lumin
Approval: see the ruleAdds a document to your workspace, either from a file address or by creating it from a template.
lumin_markdown2pdf
Approval: see the ruleConverts Markdown text into a downloadable PDF, with signature, initials, date and text fields where you placed them, and returns a link other tools can use.
lumin_generate_document_from_template
Approval: see the ruleProduces a PDF from a template, optionally filling its tags, fields and variables, and returns a download link.
send_signature_request_on_lumin
Asks you firstCreates and sends a signature request from a file, with ordered or parallel signers, viewers, custom email text and an expiry date. Your recipients get an email.
lumin_send_signature_request_from_template
Asks you firstSends a signature request directly from a template in one step, combining document generation and sending.
cancel_signature_request_on_lumin_by_id
Approval: see the ruleCancels an active signature request. Lumin says the audit trail is kept, but the cancellation cannot be undone.
lumin_post_agreement
Approval: see the ruleCreates a new AgreementGen document from a template with the data you give, including line-item tables.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone, right in the conversation.
For the two sending tools, Lumin adds its own promise: sending a request emails your recipients, so you always see the recipient list before it goes out. For the other five tools that create or cancel, no source describes a specific confirmation, and the default rule applies. On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked, and can close writing for everyone. Claude works with the rights of the Lumin account you connected, nothing more.
Which Claude plans it runs on
None of the 819 directory sheets states availability by plan, and no official source publishes it connector by connector.
The published rule is general: remote connectors like this one are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions, such as Lumin's other entry, install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members connect. For the current state, open this Lumin sheet in the official directory. Lumin itself only adds that you need a Lumin account.
Limits of the Claude Lumin connector
A connector is not an automation: Claude calls these tools while it answers you, and nothing moves on its own when a signer finishes or a request expires.
Everything on this page comes from the directory sheet and Lumin's developer documentation: neither Claude's help center nor Anthropic's developer docs cover this connector. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control a publisher's tools. For scheduled or event-driven work on your documents, the Integrations hub lists the automation pages.
Need help connecting Lumin to Claude?
A person reads every message.
