
Docjet Mcp
io.github.docjet-devPublished by GitHub account docjet-devv1.0.1Updated Oct 24, 2026
Render branded PDFs and PNG images from templates or raw HTML via the DocJet API. Free tier.
Overview
DocJet MCP lets an assistant render branded PDFs and PNG images from templates or raw HTML through the DocJet API and return signed download URLs.
- What you can do
- Render branded PDF documents such as invoices, reports and certificates from a template ID or raw HTML plus JSON data, returning a signed download URL. Render PNG images such as social or OG cards the same way. List available templates with their ID, name, description and output type. Template IDs are checked locally before any network call, and API errors come back as MCP error content with DocJet error codes.
- When to use it
- Useful when you want an assistant to generate finished documents or share images on demand — invoices, certificates, reports or social cards — without building your own rendering pipeline. It fits workflows where the output is a downloadable file rather than text.
- Requirements
- Runs locally over stdio, typically started with npx, so Node.js is needed. Requires a DocJet API key in the DOCJET_API_KEY environment variable; a free key can be obtained from DocJet. The optional DOCJET_BASE_URL variable overrides the default API endpoint. Network access to the DocJet API is required for rendering; listing templates needs no key.
Installation
In SourceWeft
- Open Docjet Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
docjet-mcp
MCP server for DocJet — render branded PDF documents (invoices, reports, certificates) and PNG social images directly from any MCP client (Claude Desktop, Claude Code, Cursor, Windsurf, ...).
Send a template ID or raw HTML plus JSON data; get back a signed download URL. Runs locally over stdio via npx — nothing to host.
Quick start
Add to your MCP client configuration:
Get an API key at docjet.dev. To try it without signing up, use the public demo key (rate-limited to 3 req/min, 50 renders/month, shared by everyone):
Tools
Example prompt once connected:
"List the DocJet templates, then render the invoice-ro template with client 'Demo SRL' and total 1000 as a PDF."
Environment variables
How it works
- Stdio transport using the official
@modelcontextprotocol/sdk(v1). render_pdf→POST /v1/render?response=url,render_image→POST /v1/image?response=url,list_templates→GET /v1/templates.- Template IDs are validated locally against
^[a-z0-9][a-z0-9-]{0,63}$before any network call. - API errors surface as MCP error content with the DocJet error code (e.g.
QUOTA_EXCEEDED,RATE_LIMITED).
Links
- API docs: docjet.dev/docs
- JS/TS SDK:
docjeton npm - Support: [email protected]
License
MIT
Source: README.md at commit 03044f6
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.