Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
Doc Generator MCP Server
First-party MCP server (source in src/index.ts) that generates print-ready HTML documents and Excel spreadsheets into an output directory. Uses StreamableHTTP transport on port 3000 (POST /mcp), with a health check at GET /health on the same port.
Available MCP Tools
| Tool | Description |
|---|---|
generate_pdf |
Converts markdown to a styled, print-ready HTML document (A4/letter @page CSS) plus a plain-text fallback |
generate_excel |
Creates a real .xlsx workbook (via ExcelJS) with styled headers, auto-width columns, alternating rows |
list_artifacts |
Lists generated files in the output directory with name, path, size, and creation date |
Honest caveat: despite the name, generate_pdf writes HTML (print-ready, for downstream PDF rendering) and a .txt fallback — it does not produce PDF binaries itself. The tool response reports format: "html".
Environment Variables
| Variable | Source | Description |
|---|---|---|
PORT |
Dockerfile default (3000) | HTTP listen port for both /mcp and /health |
OUTPUT_DIR |
Dockerfile default (/output) |
Directory where generated files are written |
No API keys or secrets are required.
Docker Build
docker build -t doc-generator-mcp:latest .
Multi-stage node:24.22.1-alpine build; runs as a non-root mcp user (uid 1001) that owns /output. That command is the only way this image comes into being: build it yourself and push it wherever your cluster pulls from.
This image is not part of the repo's image system. It has no row in deploy/images.json, no entry in the .github/workflows/build-publish.yml publish matrix, and no ghcr.io/evenfire-ai/doc-generator-mcp to pull — nothing ever pushed one. Minikube setup neither builds it nor pulls it. Its sibling MCP servers (airtable-mcp-server, web-search-mcp, playwright-server) are published to ghcr, which is what lets the evenfire registry install them on demand; this one was never published, so the row was removed rather than left pointing at an image obtainable nowhere.
Deployment
This directory has no mcpserver.yaml or NetworkPolicy — there is no ready-made McpServer CRD instance in-tree. To deploy it, write your own McpServer resource pointing at the image (see ../README.md for the CRD shape) or reference the image as an MCP workload in a workflow recipe. Generated files land in OUTPUT_DIR inside the container; mount a volume there if you need to keep or share them.
Status
Source only. The workspace package (@clerum/doc-generator-mcp) is type-checked by scripts/build-preflight.sh and formatted through scripts/prettier/paths.mjs, but no image is built, published, or deployed from it. No test suite yet (unlike airtable/ and mongodb/) and not yet referenced by user-facing docs.