Try asking
killer is the shortest form. Your agent can infer KillerNotes from a clear notes request. Use killernotes when you want to make the app explicit.
What it can do
KillerMCP gives your agent a complete local notes workflow through KillerNotes.
Works with your other Killer apps
KillerMCP uses one connection for every supported Killer app it finds. That lets an agent take a file created by one app and use its path in the next step.
Data safety and permissions
KillerNotes operations run locally through the installed app and use the vault that is currently open. Read requests return bounded results. Write and export requests change local notes or create a new file only when your agent calls the matching tool.
Your MCP client and model provider can receive note text, tags, local paths, and returned results. Review requests involving confidential notes before approving them.
How it works
Install KillerMCP once and it detects supported Killer apps on your computer. For each request, KillerMCP checks the arguments and size limits, asks KillerNotes to perform one specific operation, validates the response, and returns the result to your agent. Files exported from a note can be passed by path to another installed Killer app.
Current limits
- KillerNotes 1.3.1 or newer is required for the full tool set.
- Search queries are limited to 200 characters and result counts are bounded.
- One note response can return up to 50,000 characters.
- Exports create TXT, Markdown, HTML, KNOTE, or PDF files and refuse to overwrite an existing path.
- Encrypted KillerNotes databases cannot currently be unlocked through MCP.
