
Pdfapi Mcp Server
io.github.amranswillPublished by GitHub account amranswillv1.0.2Updated Oct 24, 2026
Generate invoice, receipt, and report PDFs from structured JSON via a single API call.
Overview
Lets an assistant generate invoice, receipt, and report PDFs from structured JSON through a single API call.
- What you can do
- This MCP server exposes PDF generation to an assistant: it takes structured JSON describing an invoice, receipt, or report and returns a finished PDF document. The registry description presents this as a single API call, so the assistant can turn structured data into a formatted document without a separate rendering step. No individual tools are listed in the manifest.
- When to use it
- Worth adding when an assistant needs to produce invoice, receipt, or report PDFs from structured data as part of a workflow, for example turning order or billing records into downloadable documents. It is a narrow, single-purpose server, so it is only useful if PDF document generation is actually part of the task.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package @aranswill/mcp-server, so Node.js and npm are needed. The manifest declares no authentication, environment variables, or headers, and it is listed as desktop only.
Installation
In SourceWeft
- Open Pdfapi Mcp Server 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
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.