notnessie

MCP tools

NotNessie exposes nine tools to Claude Code through its MCP server (registered in .mcp.json). Together they cover the two halves of project memory: retrieving context and saving durable knowledge. The signatures below come from the MCP server source.

!!! info “How Claude knows when to call them” The generated skill and CLAUDE.md block instruct Claude to retrieve context before non-trivial work and to save decisions, constraints, preferences, verified commands, and task summaries as they come up. You usually do not call these tools yourself.

Every tool accepts an optional projectPath — the absolute path to the repository — which defaults to the server’s working directory.

Retrieval tools

notnessie_get_project_context

Return the most relevant project memory for the current repository and task as a compact context pack. Claude calls this before non-trivial work.

Input	Type	Notes
projectPath	string?	Repo path; defaults to the server’s cwd.
task	string?	What you are about to work on (focuses the pack).
limit	int?	1–50 memories.
format	"markdown" | "json"?	Defaults to markdown.

notnessie_search_memory

Search project memory for a specific topic, module, file, bug, database, or API, using hybrid keyword + semantic ranking.

Input	Type	Notes
projectPath	string?	Repo path.
query	string	Required, non-empty search text.
types	string[]?	Restrict to specific memory types.
limit	int?	1–50; defaults to 8.

notnessie_get_open_questions

Return unresolved project questions Claude should be aware of.

Input	Type	Notes
projectPath	string?	Repo path.
limit	int?	1–50; defaults to 20.

notnessie_get_verified_commands

Return commands previously verified to work in this repository.

Input	Type	Notes
projectPath	string?	Repo path.
limit	int?	1–50; defaults to 50.

Save tools

All save tools redact secrets before storage and refuse credential dumps — see Privacy. Saves with the same title + type upsert in place rather than duplicating.

notnessie_save_decision

Save an architectural or implementation decision made during the session.

Input	Type	Notes
title	string	Required.
summary	string	Required.
reasoning	string?	Why the decision was made.
topic	string?	Grouping topic.
appliesToFiles	string[]?	Files the decision affects.
sessionId	string?	Provenance.
task	string?	Provenance.
projectPath	string?	Repo path.

notnessie_save_preference

Save a user or project coding preference.

Input	Type	Notes
title	string	Required.
summary	string	Required.
topic	string?	Grouping topic.
sessionId	string?	Provenance.
projectPath	string?	Repo path.

notnessie_save_constraint

Save a hard project rule Claude should follow later.

Input	Type	Notes
title	string	Required.
summary	string	Required.
severity	"low" | "medium" | "high"?	How strict the rule is.
appliesTo	string[]?	What the rule applies to.
sessionId	string?	Provenance.
projectPath	string?	Repo path.

notnessie_save_verified_command

Save a command that successfully worked in this repository.

Input	Type	Notes
command	string	Required.
purpose	string?	What the command is for.
exitCode	int?	The exit code observed.
projectPath	string?	Repo path.

notnessie_save_task_summary

Save a useful summary after a coding task: what changed, commands run, the outcome, and new TODOs.

Input	Type	Notes
task	string	Required.
summary	string	Required.
filesChanged	string[]?	Files touched.
commandsRun	string[]?	Commands executed.
outcome	string?	How it ended.
newTodos	string[]?	Follow-ups discovered.
sessionId	string?	Provenance.
projectPath	string?	Repo path.

Errors and safety

Save tools return a clear error rather than storing anything when:

• input contains a blocked secret (a private key, a credential-bearing connection string, or an .env dump), or
• a required field is empty or whitespace-only.

This keeps secrets out of the store and gives Claude actionable feedback at the tool boundary.

This site is open source. Improve this page.