Lumin
by Lumin
Send documents for e-signature, track them, and generate agreements from templates in an AI agent. 14 tools, matched exactly by Lumin's own published list. OAuth with real read and write scopes.
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.
Connect Lumin via MCP
https://mcp.luminpdf.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Lumin Tools & Capabilities (14)
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_luminsucceeds, 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:requestsgrants 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
readOnlyHintvalue 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_markdown2pdfis 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
verificationfield 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
viewersandcustom_emailfields 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
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.
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.
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.
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.
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.
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.
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.
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
- Lumin developer documentation, "Supported Tools" (retrieved 2026-08-22). This is the vendor tool enumeration diffed above. · retrieved 2026-08-22
- Lumin developer documentation, "Connecting to Lumin MCP" (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin developer documentation, "Common MCP Client" (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin documentation index,
llms.txtandllms-full.txt— · (retrieved 2026-08-22) · retrieved 2026-08-22 - Lumin OpenAPI specification (retrieved 2026-08-22). Source for the request schemas, the endpoint inventory and the per-endpoint scope requirements. · retrieved 2026-08-22
- Lumin OAuth 2.0 guide and scope table (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin API changelog (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin help centre, "How do I get my Lumin Sign Certificate of Completion?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin help centre, "What counts as a completed document?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin help centre, "What do I do if my document has expired?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Lumin help centre, "How do I reschedule a deadline for an expired/overdue document?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous
initializereturned 401 with a www-authenticate header naming , and that descriptor plus the authorization server metadata at were read directly (2026-08-22) · retrieved 2026-08-22 developers.luminpdf.com/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis of this documentation is expressly permitted by the publisher (retrieved 2026-08-22) · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Lumin support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Lumin
- Tools
- 14
- Domain
- mcp.luminpdf.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.