fnaze MCP server
Commit Nov 12, 2026Lets AI agents and developers document file-by-file changes by describing what changed and why for every modified file.
Also known as amisonnet8/fnaze
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 12, 2026
- License
- MIT
What is fnaze MCP?
fnaze lets AI agents and developers document file-by-file changes by describing what changed and why for every modified file.
Summary generated from the project's README
About fnaze MCP server
Developers and AI agents can use fnaze to document file-by-file changes by recording exactly what was modified and why. Unlike standard commit messages that summarize an entire set of changes, this tool maintains a description file containing one line per modified file. This allows reviewers to quickly understand the intent behind specific edits across a codebase.
Users can run fnaze as a local CLI or as an MCP server. When configured as an MCP server with the --allow-write flag, AI agents gain access to tools like new_group, set_title, set_description, and remove_description to manage documentation directly within the .fnaze/ directory. The server supports multiple languages simultaneously, ensuring that descriptions in different languages stay in sync. It provides commands such as show to view changes as a tree, status to check for missing descriptions or language mismatches, and log to list previous change groups.
What you can do with it
- 1Documenting staged file changesAn AI agent can look at staged files and create a detailed description for each one.
- 2Reviewing change intentReviewers can use the show command to see a tree view of what changed and why.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableamisonnet8/fnaze is public and reachablegithub.com/amisonnet8/fnaze ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/amisonnet8/fnaze ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub日本語 | English
Describe each set of changes file by file — what changed and why, one line each.A CLI and MCP server.
Demo · Features · Install · Quick start · Usage · With git and AI agents · Docs
A commit message speaks for the whole set of changes at once; why each file was changed is left out. fnaze keeps, for one set of changes, a description file with one line per changed file saying what changed there and why. A reviewer reads that list to see where to look, and why.
🎬 Demo
new starts a group of description files (here in en and ja), carrying over the paths of the last one. title and set write it, and status reports what is left: here the Japanese file is not written yet. show prints one file as a tree, and log lists the groups. The image is made by a test from fnaze's real output.
✨ Features
- 📝 One line per file: for each changed file, what changed and why. A detail line can follow for the longer story
- 👀 Made to be read:
showprints the file as a tree, with the descs in one column - 🗂️ Less to write for big changes: a desc on a directory covers everything under it, and a pattern (
*_test.go) covers the files it matches - 🌐 Several languages, kept in step: one file per language in a group.
statusreports the files of a group whose paths differ - 🩺 Checks for hooks and CI:
status --requirefails on an empty title, an entry without a desc, a broken file or a language mismatch - 🔌 A built-in MCP server: with
fnaze mcp, AI agents get the same features, with the same JSON as--json - 🔒 No git, nothing outside
.fnaze/: fnaze does not read or run git, or any other program. What one set of changes is (usually one commit) is up to you - 📦 A single binary: written in Go, for Linux, macOS and Windows
📦 Install
Download the archive for your OS (Linux, macOS or Windows; amd64 or arm64) from Releases, and put fnaze (fnaze.exe on Windows) somewhere on your PATH. checksums.txt there lets you check the archive. The archive also holds the license texts of the libraries built into fnaze (licenses/).
With Go 1.27 or later, you can also build it yourself:
go install github.com/amisonnet8/fnaze/cmd/fnaze@latest
fnaze completion <shell> prints a completion script for bash, zsh, fish or powershell. It completes the commands, the options, the languages, the groups, and the paths of the file with their descs. See Commands for where to put it.
🚀 Quick start
cd your-project
fnaze init # make .fnaze/
fnaze new # start a group (in en)
fnaze title "Extend the session lifetime on access"
fnaze set src/auth/session.go "Extend the lifetime on every access"
fnaze set config/auth.yaml "Set the default session.ttl to 30m" \
--detail "Users reported sessions expiring too soon"
fnaze status --require # anything left to write?
fnaze show # read it back
For several languages, start the group with fnaze new en ja, and write each one with --lang ja. The next fnaze new uses the languages of the last group.
🧭 Usage
A description file is plain text in .fnaze/changes/<datetime>_<UUID>[_<language>].txt: the title, then one entry per line, indented with tabs. An indented path is joined to the path of the directory entry above it.
# Extend the session lifetime on access instead of fixing it
src/
auth/ Change the session lifetime from fixed to extended
session.go Extend the lifetime on every access
*_test.go Add tests for the extension
config/auth.yaml Set the default session.ttl to 30m
| Users reported sessions expiring too soon
docs/old.md Removed; its content moved to docs/auth.md
show prints it with the descs in one column (here the older of the two groups of docs/examples/changes/, given by its short name):
$ fnaze show 20261107T003426Z_8980
# Extend the session lifetime on access instead of fixing it
src/
auth/ Change the session lifetime from fixed to extended
session.go Extend the lifetime on every access
*_test.go Add tests for the extension
config/auth.yaml Set the default session.ttl to 30m
| Users reported sessions expiring too soon
docs/old.md Removed; its content moved to docs/auth.md
log lists the groups, newest first (the times are in the local time zone, here TZ=Asia/Tokyo):
$ fnaze log
20261107T021530Z_2c4c 2026-11-07 11:15 en,ja 3 Log session extensions
20261107T003426Z_8980 2026-11-07 09:34 en,ja 6 Extend the session lifetime on access instead of fixing it
| Command | What it does |
|---|---|
fnaze init |
Makes .fnaze/ |
fnaze new [language…] |
Starts a group, one file per language, with the paths of the last file of each language |
fnaze title <title> |
Writes the title |
fnaze set <path> <desc> [--detail <detail>]… |
Writes one entry (and its detail) |
fnaze rm <path> |
Removes one entry |
fnaze status [--require] [--all | group] |
Reports format errors, empty titles, empty descs and language mismatches |
fnaze show [group] |
Shows one file as a tree |
fnaze log |
Lists the groups, newest first |
fnaze mcp [--allow-write] |
Runs as an MCP server |
fnaze completion <shell> |
Prints a completion script |
The commands that work on a language take --lang <language> (new takes them as arguments), or else use FNAZE_LANG, or else en. Every command but completion takes -C <dir>, and the reading and writing commands print JSON with --json. See Commands and File format for more.
🤝 With git and AI agents
fnaze does not decide what one set of changes is, and does not read git. A common way is one group per commit, put in the commit itself:
- Stage the changes, and look at
git diff --cached --name-only fnaze new, thenfnaze titleandfnaze setfor each changed file (an AI agent can do this through the MCP tools)fnaze status --require, then commit the description files with the changes- The reviewer reads
fnaze show(or the file in the pull request)
docs/examples/pre-commit stops a commit that adds no description file, or whose newest group fnaze status --require reports. Copy it to .git/hooks/pre-commit and make it executable. fnaze does not require it.
{
"mcpServers": {
"fnaze": {
"command": "fnaze",
"args": ["mcp", "--allow-write"]
}
}
}
The reading tools are show, status and log. With --allow-write, the writing tools new_group, set_title, set_description and remove_description are offered too, and they write only inside .fnaze/. One server serves every language: each tool takes the language as an argument. See Commands for more.
## When committing
- Look at the staged files with `git diff --cached --name-only`.
- Start a group with `fnaze new`, write its title with `fnaze title`,
and write one line per changed file with `fnaze set <path> <desc>`:
what changed there, and why.
- Remove the carried-over paths that did not change with `fnaze rm <path>`.
- Run `fnaze status --require`, and commit `.fnaze/` with the changes.
📚 Docs
| 💬 Interactive guide | Ask questions to learn about fnaze (made with Gemini Notebook) |
| 🏛️ docs/design/overview.md | Design: what fnaze is for, and what it leaves out |
| 📐 docs/reference/file-format.md | Where the files are, their names, and how they are written |
| 📐 docs/reference/commands.md | The commands, the JSON, the MCP tools and completion |
| 🧪 docs/examples/ | Example description files and a git pre-commit hook |
📄 License
fnaze MCP questions
Does fnaze interact with git?
No, fnaze does not read or run git or any other program; it only manages description files within the .fnaze/ directory.