Lets an AI client edit Markdown invoice templates, generate PDFs, and inspect visual previews using headless Chrome.
Also known as vijayst/invoice, invoice, @vijayst/invoice-studio
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Sep 23, 2026
- License
- —
What is Invoice Studio MCP?
Invoice Studio lets an AI client edit Markdown invoice templates, generate PDFs, and inspect visual previews using headless Chrome.
Summary generated from the project's README
About Invoice Studio MCP server
Invoice Studio provides an environment for developers to design and automate invoice generation using AI clients like Claude Desktop, Cursor, or Windsurf. The server operates over stdio and allows an agent to interactively modify Markdown or Handlebars templates and CSS files. By using headless Chrome for rendering, the system can produce high-quality PDF documents and visual PNG previews for immediate inspection.
Users can choose from three distinct generation pipelines depending on their technical needs. The standard pipeline combines Markdown with Handlebars and JSON data, while a second option utilizes Handlebars with Tailwind CSS via a CDN. A third method allows for raw Markdown editing without external data files. This setup is ideal for developers who want to iterate on document layouts through natural language commands rather than manual coding. To function, the environment requires Node.js and a local installation of Chrome or Chromium.
What you can do with it
- 1Iterative template stylingAsk the AI to modify the CSS or Markdown structure and immediately view the visual changes.
- 2Automated monthly billingRun a headless command to turn updated JSON data into a finished PDF invoice.
- 3Tailwind CSS integrationUse utility classes within Handlebars templates to style invoices via a web-based CDN.
Written from the project's README. Every use case is checked against a quote from it.
How to install Invoice Studio MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Invoice Studio MCP in Claude Code
$ claude mcp add invoice -- npx -y @vijayst/invoice-studioInstall Invoice Studio MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"invoice": {
"command": "npx",
"args": [
"-y",
"@vijayst/invoice-studio"
]
}
}
}Install Invoice Studio MCP in VS Code
.vscode/mcp.json
{
"servers": {
"invoice": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vijayst/invoice-studio"
]
}
}
}Install Invoice Studio MCP in VS Code CLI
$ code --add-mcp '{"name":"invoice","type":"stdio","command":"npx","args":["-y","@vijayst/invoice-studio"]}'Install Invoice Studio MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"invoice": {
"command": "npx",
"args": [
"-y",
"@vijayst/invoice-studio"
]
}
}
}Install Invoice Studio MCP in Codex
$ codex mcp add invoice -- npx -y @vijayst/invoice-studioInstall Invoice Studio MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.invoice] command = "npx" args = ["-y", "@vijayst/invoice-studio"]
Install Invoice Studio MCP in Gemini CLI
$ gemini mcp add -s user invoice npx -- -y @vijayst/invoice-studioInstall Invoice Studio MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"invoice": {
"command": "npx",
"args": [
"-y",
"@vijayst/invoice-studio"
]
}
}
}Configuration
CHROME_PATH
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablevijayst/invoice is public and reachablegithub.com/vijayst/invoice ↗Pass
- Package names this repository as its source@vijayst/invoice-studio names vijayst/invoice as sourcenpmjs.com/package/@vijayst/invoice-studio ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-09-23github.com/vijayst/invoice ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @vijayst/invoice-studioPass
- No critical advisory in the package or its dependencies237 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubInvoice Studio
Invoice templates with an MCP server for interactive editing (Claude Desktop / Cursor / Windsurf) and three headless generate pipelines for monthly PDF runs.
Agents: see AGENTS.md for the edit → generate → preview workflow. Registry → PDF → fork: USER-JOURNEY.md.
How it works
Phase 1 — Interactive studio: an AI client connects to the MCP server over stdio. You ask it to tweak the template or styles, regenerate, and inspect the preview PNG until the layout looks right.
Phase 2 — Monthly execution: pick one of the three generate commands below. The default pipeline updates src/data/invoice-input.json (or injects it from CI), then runs npm run generate to produce output/invoice.pdf and output/preview.png.
Markdown + Handlebars (npm run generate)
src/templates/invoice.md ← Markdown template ({{placeholders}} for data)
src/styles/invoice.css ← Print styles
src/data/invoice-input.json
│
▼ npm run generate
output/invoice.md ← rendered markdown
output/invoice.html
output/invoice.pdf
output/preview.png ← used by get_invoice_preview
Handlebars fills src/templates/invoice.md from src/data/invoice-input.json. Marked turns that Markdown into HTML, src/styles/invoice.css styles it, and headless Chrome writes the PDF and preview.
Handlebars + Tailwind CDN (npm run generate:hbs)
src/templates/invoice.hbs ← HTML template ({{placeholders}} + Tailwind classes)
src/data/invoice-input.json
│
▼ npm run generate:hbs
output/invoice-hbs.html
output/invoice-hbs.pdf
output/preview-hbs.png
scripts/generate-invoice-hbs.js compiles src/templates/invoice.hbs with the same JSON. Styling is Tailwind utility classes in the template. The page loads Tailwind from https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4, so this command needs network access. The script does not compile a CSS file.
Raw Markdown (npm run generate:raw)
src/templates/invoice-raw.md ← Markdown with invoice values written in
src/styles/invoice.css
│
▼ npm run generate:raw
output/invoice-raw.html
output/invoice-raw.pdf
output/preview-raw.png
src/templates/invoice-raw.md contains the invoice text itself (dates, amounts, parties, line items). scripts/generate-invoice-raw.js converts that file with Marked and src/styles/invoice.css. This path does not read invoice-input.json and does not run Handlebars. Change the Markdown when the month’s values change.
Setup
npm install
npm run build:mcp
Chrome or Chromium is required for PDF/PNG rendering. The generate script finds common install paths (macOS / Linux / Windows). If needed:
export CHROME_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
Generate an invoice (headless)
Markdown + Handlebars
- Edit monthly fields in
src/data/invoice-input.json(amounts, dates, line items, etc.). - Optionally adjust layout in
src/templates/invoice.mdorsrc/styles/invoice.css. - Run
npm run generate.
Handlebars + Tailwind
- Edit
src/data/invoice-input.jsonfor monthly values. - Adjust layout with Tailwind classes in
src/templates/invoice.hbs. - Run
npm run generate:hbs(requires network so Chrome can load the Tailwind CDN).
Raw Markdown
- Edit the values directly in
src/templates/invoice-raw.md. - Optionally adjust
src/styles/invoice.css. - Run
npm run generate:raw.
Artifacts land in output/.
Use the MCP to edit and generate
1. Build and point your client at the server
npm install
npm run build:mcp # required — creates dist/index.js
Cursor (recommended): this repo includes .cursor/mcp.json. Open the project folder in Cursor, then reload MCP / the window. It uses ${workspaceFolder}/dist/index.js so the path is always the repo root.
If you configure MCP manually in Cursor Settings, use the absolute path to dist/index.js (relative dist/index.js alone resolves under your home directory and fails):
{
"mcpServers": {
"invoice-studio": {
"command": "node",
"args": ["/Users/YOU/Documents/invoice/dist/index.js"]
}
}
}
Claude Desktop — in claude_desktop_config.json (absolute paths required):
{
"mcpServers": {
"invoice-studio": {
"command": "node",
"args": ["/Users/YOU/Documents/invoice/dist/index.js"]
}
}
}
The server locates the repo from its own script path, so tools always read/write this project even if the client’s cwd is wrong.
Public MCP Registry
Registry name: io.github.vijayst/invoice-studio (npm: @vijayst/invoice-studio). After publish, search the official MCP Registry.
Clients that install from the registry typically run:
{
"mcpServers": {
"invoice-studio": {
"command": "npx",
"args": ["-y", "@vijayst/invoice-studio"]
}
}
}
npx runs a copy of this repo (sample data included). You can generate output/invoice.pdf in that copy, then fork this repo and export the template into the clone.
Full walkthrough: USER-JOURNEY.md.
2. Interactive edit loop
Ask the model something like:
Read
src/templates/invoice.mdand tighten the payment section. Regenerate and show me the preview.
Typical tool sequence:
| Tool | Purpose |
|---|---|
read_template_file |
Read src/templates/invoice.md or src/styles/invoice.css |
write_template_file |
Write updated template/CSS |
run_generate_build |
Runs npm run generate → PDF + output/preview.png |
get_invoice_preview |
Returns the preview PNG for visual review |
get_git_status |
Check what changed before committing |
get_workspace_root |
Show the npx or clone directory this server is using |
export_studio_to_repo |
Copy template/CSS/data from this workspace into a cloned fork |
Repeat edit → generate → preview until satisfied, then commit.
3. Scripts reference
| Script | Command |
|---|---|
| Build MCP | npm run build:mcp |
| Start MCP (stdio) | npm run start:mcp |
| Markdown + Handlebars PDF | npm run generate |
| Handlebars + Tailwind CDN PDF | npm run generate:hbs |
| Raw Markdown PDF | npm run generate:raw |
Project layout
├── smithery.yaml
├── package.json
├── src/
│ ├── templates/invoice.md
│ ├── templates/invoice.hbs
│ ├── templates/invoice-raw.md
│ ├── styles/invoice.css
│ ├── data/invoice-input.json
│ └── mcp/index.ts
├── scripts/generate-invoice.js
├── scripts/generate-invoice-hbs.js
├── scripts/generate-invoice-raw.js
└── output/preview.png
Invoice Studio MCP questions
How do I add Invoice Studio MCP to Claude Code?
Run claude mcp add invoice -- npx -y @vijayst/invoice-studio in your terminal. Add --scope user to make it available in every project.
How do I add Invoice Studio MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What is required for PDF and PNG rendering?
Chrome or Chromium must be installed on your system for the rendering process to work.
Does the Tailwind template require internet access?
Yes, the Handlebars + Tailwind CDN pipeline requires network access to load Tailwind from the jsdelivr CDN.
Can I preview the invoice layout visually?
Yes, you can use the get_invoice_preview tool to return a preview PNG for visual review.