Registers the KillerMCP server with GitHub Copilot when the client is found, enabling access to KillerTools and Killer app family tools through Copilot.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@KillerMCP merge the PDF files in my Downloads folder into one document"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
One local MCP connection for KillerTools and the Killer app family: KillerPDF, KillerNotes, KillerScan, KillerShell, Killendar, and KillerBench.
KillerMCP is a native .NET 10 host. It detects supported Killer apps, exposes their available commands, and registers one MCP server with compatible agent clients. The separate KillerTools repository provides the shared engine for the website utilities.
Download the signed KillerMCP installer, run setup, then open a new agent chat. Setup checks for the .NET 10 runtime and registers KillerMCP with Codex, Claude Code, Claude Desktop, Cursor, GitHub Copilot, Gemini CLI, and Windsurf when those clients are found.
You can also install it with WinGet or Chocolatey. Both install the .NET 10 Desktop Runtime for you when it is missing.
winget install SteveTheKiller.KillerMCP
choco install killermcpFully quit and reopen an agent client after setup or upgrade, then start a new chat. In Claude Desktop, KillerMCP appears under Settings > Developer as a running local server and under Connectors as a desktop connector. Cowork can use that local connection without a separate plugin.
Once connected, ask naturally:
killer domain search example.com
killer merge these PDFs
killerscan my network
killer update status
The server supplies tool descriptions and instructions that help the client select the appropriate tool. Client behavior varies, so these phrases are guidance rather than guaranteed commands.
KillerMCP checks GitHub Releases hourly and shows a Black/Fuchsia update window when a newer version is available. Choose whether future updates should stay off, check and ask, download and ask, or install automatically. Every downloaded installer must match the published SHA256 and pass Windows signature verification before it can run.
Related MCP server: Cupertino
All 81 KillerTools website utilities from the native KillerTools engine.
Automatic tool discovery for supported versions of KillerPDF, KillerScan, KillerNotes, KillerShell, Killendar, and KillerBench.
Safe migration from the earlier Node based KillerMCP installation and client registrations.
Install, reinstall, repair, and uninstall behavior through the KillerUI styled Windows setup.
A framework dependent native package for each supported operating system and processor architecture.
KillerPDF provides PDF editing, conversion, inspection, OCR, printing, and accessibility tools when the installed version advertises them. KillerScan provides local network details, bounded scans, host probes, offline MAC vendor lookup, ping, route tracing, diagnostics, availability watching, and KillerSpeed tests. KillerShell provides read-only file browsing, text reading, file hashing, process and service listings, event log reading, registry inspection, and drive information. KillerNotes can search, read, create, edit, organize, color, import images, inspect links and history, and export notes. Killendar provides agenda lookup and creates single appointments while its window is open and unlocked.
KillerBench provides offline Windows code lookups, read-only checks and full diagnostic scans. It can also preview and run a fixed list of guarded Windows repairs. Repairs are off until you turn them on in the KillerMCP section of the KillerBench About window. Every repair needs a fresh preview, Windows administrator approval, and for disruptive repairs your approval in a KillerMCP window on the desktop. See KillerBench for the full list and safeguards.
Cross app workflows can export a KillerNotes note, KillerScan network report, Killendar agenda, or KillerShell directory listing to PDF. They can also save scan, agenda, and directory reports as notes, or render selected KillerPDF pages into image notes.
See What KillerMCP can do for the complete tool guide, examples, limits, and data handling details.
For tool permissions and invocation logging, see Tool permissions and visibility and Tool call history.
Clone this repository with its pinned KillerTools engine source:
git clone --recurse-submodules https://github.com/SteveTheKiller/KillerMCP.git
cd KillerMCPBuild and test the native host:
dotnet build KillerMCP.slnx -c Release
powershell -NoProfile -File scripts\Test-All.ps1Build a framework dependent package for the current platform:
powershell -NoProfile -File scripts\Test-NativePackage.ps1Build and test the Windows installer:
powershell -NoProfile -File scripts\Test-WindowsInstaller.ps1The native host requires the .NET 10 runtime. The Windows installer checks for it before installation and links to the official Microsoft download when it is missing.
For development builds or custom app locations, set KILLERPDF_CLI, KILLERSCAN_CLI, KILLERNOTES_CLI, KILLENDAR_CLI, KILLERSHELL_CLI, or KILLERBENCH_CLI to an absolute executable path. An invalid override leaves that app unavailable instead of silently selecting another copy.
Run powershell -NoProfile -File release.ps1 to build, sign, verify, test, and publish the release. The reviewed source must be on origin/main and the changelog entry must be dated for release. Use -DryRun to stop before tagging and publishing. -SkipSign produces an unsigned local test build and never publishes.
Public installers are published through KillerMCP releases.
KillerMCP is licensed under the GNU General Public License Version 3.
This server cannot be deployed
61 text, security, converter, calculator, and PDF tools -- callable via MCP on one host.
Notes, files, GitHub, and Drive through one MCP connection.
Notes, files, GitHub, and Drive through one MCP connection.
Notes, files, GitHub, and Drive through one MCP connection.