leafwright
MCP server by Leafwright · mcp
Leafwright renders HTML, public URLs, and published Handlebars templates into PDFs, and returns a signed download link. Every render is a tracked job with readable logs, so when a layout breaks you can read the cause — a font that 404'd, an asset that timed out, content overflowing the page — and repair the template from it. Two ways to authenticate. Either follow the 401: any other tool answers 401 with a WWW-Authenticate header naming the OAuth discovery document, and a client that supports OAuth 2.1 registers itself from there. Or call leafwright_login, which needs no token, show the returned verification_url and user_code to the person, and once they approve call leafwright_auth_status with the device_code it gave you. Keep that device_code: this transport stores nothing between requests. Until a token is in hand only the login tools are listed. That means unauthenticated, not empty: the document tools appear once authentication completes.
Endpoint: https://leafwright.co/mcp
Verification: observed. Source: crawl.
Capabilities (3)
- leafwright_login
- leafwright_auth_status
- leafwright_logout