Lumin MCP Server

The Lumin MCP server is the official remote MCP integration from Lumin PDF, exposing the Lumin API to MCP-compatible AI assistants like Claude Desktop and Cursor. It lets agents manage documents, send and track e-signature requests, list workspaces, upload files, and convert Markdown content into rendered PDFs, all through natural-language commands.

The server is hosted by Lumin at https://mcp.luminpdf.com/mcp and is connected via the mcp-remote proxy, with authentication handled through Lumin's OAuth flow (credentials are cached under ~/.mcp-auth/). The companion GitHub repo at luminpdf/lumin-mcp-server documents the seven available tools and provides Claude Desktop and Cursor setup instructions.

It is most useful for teams that already rely on Lumin for PDF editing and e-signatures and want to drive those flows from an AI assistant, for example, drafting a contract in Markdown, converting it to PDF, uploading it to a workspace, and sending it for signature in a single agent run.

Tools

Prerequisites

• A Lumin account (sign in at luminpdf.com)
• Node.js installed locally (required for the npx mcp-remote proxy)

Claude Desktop

Edit your claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%/Claude/claude_desktop_config.json

Add the Lumin entry:

{
  "mcpServers": {
    "lumin": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.luminpdf.com/mcp"]
    }
  }
}

Restart Claude Desktop. On first use, the mcp-remote proxy opens a browser window to complete the Lumin OAuth flow.

Cursor

Installation is handled automatically via the integration link provided in the Lumin MCP repo. If authentication misbehaves, clear cached credentials at ~/.mcp-auth/ and restart Cursor.

Reference

Full Lumin API documentation: https://developers.luminpdf.com/api/

• Draft a contract in Markdown, convert it to PDF with lumin_markdown2pdf, upload it to a workspace, and send it out for e-signature in one agent run.
• Monitor outstanding signature requests by ID, fetch their status, and cancel ones that have expired or are no longer needed.
• Bulk generate branded PDFs from Markdown content (proposals, NDAs, statements of work) without leaving the AI assistant.
• Inspect Lumin workspaces and the current user's profile to route documents to the correct team workspace before sending.
• Build approval workflows where an agent prepares a document, validates signer details, and only dispatches the signature request after a human confirmation.

• "Convert this Markdown into a PDF using Lumin and send it for signature to alice@example.com and bob@example.com with a 7 day expiry."
• "List all my Lumin workspaces and tell me which one has the most recent uploads."
• "Check the status of Lumin signature request sr_12345 and cancel it if it has not been signed yet."
• "Upload the attached contract PDF to my 'Sales' workspace in Lumin."
• "Generate a one page summary PDF from this Markdown and give me the download URL."

• Official, provider-hosted server maintained by Lumin, no self-hosting required.
• Covers the full e-signature lifecycle: send, fetch, cancel, plus file upload and workspace listing.
• Built-in Markdown to PDF conversion makes it easy to compose documents directly in an agent and ship them as polished PDFs.
• OAuth-based auth via mcp-remote means no manual API key management.

• Tool surface is relatively small (seven tools); advanced Lumin PDF editing operations exposed by the REST API are not all surfaced.
• Requires Node.js locally because the connection goes through the npx mcp-remote proxy.
• Documentation in the GitHub repo is minimal; deeper parameter details require consulting the separate Lumin developer API docs.

• DocuSign MCP integrations for teams already standardized on DocuSign e-signatures.
• markdown2pdf-mcp for local, offline Markdown to PDF conversion without an external service.
• Dropbox Sign (HelloSign) API wrapped via a custom MCP server for alternative e-signature flows.