Try asking:
killer is the shortest form. Your agent can infer KillerPDF when the request and attached files are clearly about PDFs. Use killerpdf only when you want to make the app explicit.
What it can do
Data safety and permissions
PDF operations run locally through the installed KillerPDF app. File-producing tools stage their output and refuse to overwrite an existing path. Preflight and accessibility checks are read-only. Printing sends a real local print job. OCR can download a selected language model from the Tesseract project on first use.
Your MCP client and model provider can still receive file paths and returned report data. Review the requested paths, printer, and operation before approval and apply the provider data handling rules to confidential documents.
How it works
KillerMCP is an open-source local runtime. It includes all 81 KillerTools utilities, detects installed Killer apps, and exposes only the adapters supported by those versions. It validates paths and limits before calling KillerPDF, stages new output, and validates the result.
Current limits
Each source PDF is limited to 64 MiB. Merge accepts 2 to 8 PDFs with combined inputs up to 128 MiB. Page ranges, DPI, copy counts, render sizes, and benchmark page counts are bounded. Password protected files require the correct password. OCR may require a language download. Preflight and accessibility reports appear only when the installed KillerPDF build advertises them.
One connection for the family
Install KillerMCP once. It detects supported Killer apps on your computer and adds their tools to one agent connection. As more app integrations are released, the same KillerMCP runtime can provide them without a separate installer for every app.
