Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @invoicepdfs/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add invoicepdfs-mcp -- npx -y @invoicepdfs/mcp@0.1.2รันในเทอร์มินัล
{ "mcpServers": { "invoicepdfs-mcp": { "command": "npx", "args": [ "-y", "@invoicepdfs/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Gives an AI agent the InvoicePDFs API as tools: render a document, check it for e-invoicing compliance, manage customers, and reach the rest of the API on demand.
It is an ordinary HTTPS client of the public API. No database, no extra service
to deploy, nothing added to render.yaml. It runs on your machine.
MCP server for the InvoicePDFs API
Add to your MCP client's configuration — Claude Desktop, Cursor, or anything else that speaks MCP over stdio:
{
"mcpServers": {
"invoicepdfs": {
"command": "npx",
"args": ["-y", "@invoicepdfs/mcp"],
"env": { "INVOICEPDFS_API_KEY": "inv_live_..." }
}
}
}
Create a key at https://invoicepdfs.com. INVOICEPDFS_BASE_URL overrides the
host if you are pointing at a local server.
An API key is not scoped. Any key you give this server can do anything your account can, including deleting data. That is a property of the key, not of this server — there is no narrower credential to hand it. Your MCP client will still ask before each tool call.
Thirty tools. Twenty-seven name a common operation outright —
document_render, document_create, compliance_check, customer_list and so
on — document_transition covers the seven-state document lifecycle through one
to argument, and two reach everything else:
find_operation — search all 161 operations by what they do and get the
full input schema of each match.call_operation — run one of them.The whole API is reachable; only the common path is listed up front. Every client caps the tool list (Cursor around 40, Junie 100, Copilot 128), so a server advertising 161 tools would either break or crowd out every other server you have connected.
document_render renders asynchronously and waits for the result, so it returns
a finished render rather than a queued one. Rendering is CPU-bound and served by
a single worker, so prefer one render at a time over starting many in parallel.
The tool surface is built from openapi.json at startup. src/operations.ts
reads the spec and derives each operation's name, input schema and description;
src/client.ts is one executor that can run any of them. Adding an endpoint to
the API adds a working tool with no code change here.
It is built at runtime rather than generated into a committed file on purpose. The first version of this emitted 16,000 lines of TypeScript that had to be regenerated and committed whenever the API changed — a second copy of the spec, with its own way of going stale. Parsing the spec costs about 10ms, once, in a process that starts once.
Only three things are written by hand:
Tool descriptions come from the API's handler docstrings, through the spec. They are not written here, because prose about an operation kept in two places drifts.
npm install
npm test # drift and tool-surface checks
npm run build # compiles
npm pack # vendors openapi.json into the tarball, then cleans up
This repository is generated. The source lives in the InvoicePDFs API
monorepo under mcp/, and every commit here is a sync from there — so a change
made in this repository is overwritten by the next one. Open an issue instead
and it gets made where it survives.
The reason for the split is that the two things want different homes. The code
belongs next to the API it describes: tool descriptions are the API handlers'
own docstrings, and npm test fails when the manifest names an operation the
spec no longer has, which is a guard that only works if it runs in the pull
request that renames the handler. The package belongs in a public repository,
because npm build provenance requires one, and because a registry listing with
no readable source behind it is worth less.
So the drift guard runs upstream on every API change, and this repository publishes.
{ "mcpServers": { "invoicepdfs-mcp": { "command": "npx", "args": [ "-y", "@invoicepdfs/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@invoicepdfs/mcp ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 MCP server for the InvoicePDFs API