Try asking:
killer is the shortest form. Your agent can infer KillerShot from a clear screenshot or recording request. Use killershot when you want to make the app explicit.
What it can do
KillerMCP exposes ten KillerShot tools.
Data safety and permissions
KillerShot runs on your computer and saves its captures there. The tools return file paths, not pictures, so the image stays on your PC unless your agent opens the file. A screenshot can show anything on the screen, including other apps and private information, so review each capture request before you approve it. Agent captures leave the clipboard alone and play no camera sound unless the request asks for the clipboard.
How it works
KillerMCP is a small program that lets your AI assistant use supported Killer apps installed on your computer. You install and connect it once, and it automatically finds the apps and tools available on your computer. When you ask for a screenshot, KillerMCP checks the request, runs KillerShot's command line in its own process, waits for it to finish, and gives the saved file's path back to your assistant. The capture is taken by the installed KillerShot app, not by this webpage, and a KillerShot already running in the tray is left alone.
Current limits
Output paths must be absolute, and an existing file is never replaced. Screenshots can wait up to 30 seconds before capturing. Recordings last 1 to 300 seconds. MP4 recordings larger than 4096 x 2304 pixels are scaled down to fit. Window and monitor names come from the list tools. The region selector and window picker are not offered to agents, because they need you at the screen.
Why KillerMCP runs twice
Claude Desktop starts each local MCP server twice. One copy serves the app's own chats, and the other serves Claude sessions that use this computer remotely. Seeing two KillerMCP.exe processes under Claude in Task Manager is normal. KillerMCP is not installed twice, and nothing needs to be fixed.
