TL;DR: 3.3.0 brings gemini-faf-mcp to Antigravity CLI: install it as a plugin and it works in your project. Simple.
agy plugin install https://github.com/Wolfe-Jam/gemini-faf-mcp
Open source (MIT): https://github.com/Wolfe-Jam/gemini-faf-mcp
Then run /setup in your project. Moving from Gemini CLI: agy plugin import gemini.
In plain English
Old state. Google replaced Gemini CLI with Antigravity CLI (agy). gemini-faf-mcp was a Gemini CLI extension. Antigravity starts a plugin's server inside the plugin's own folder, so the server couldn't see your project.
Fix. The plugin now starts the server so that it knows the folder you ran agy in, and works there.
New state. One install command, then /setup in your project. It finds your project.faf and writes to your project, never to its own folder.
What it does
gemini-faf-mcp keeps your project's facts (the stack, the goal, how to run the tests) in one small YAML file in the repo, project.faf. Its MCP tools read it, score how complete it is, and write GEMINI.md or AGENTS.md from it, keeping the rest of those files as you wrote them. Python, FastMCP, 13 tools, MIT.
3.2.1 vs 3.3.0 under Antigravity
| Under Antigravity CLI | 3.2.1 | 3.3.0 |
|---|---|---|
agy plugin install |
installs | installs |
finding your project.faf
|
found the plugin's own file | finds yours |
writing project.faf, GEMINI.md
|
went into the plugin's folder | go into your project |
The bug that cost a release
3.2.1 taught the server to find your project when Antigravity starts it in the plugin folder: Antigravity sets PLUGIN_ROOT, and the server reads your project from the inherited PWD, with guards so it never widens to $HOME or /.
That shipped, and then did nothing on a real install. The plugin ran uvx gemini-faf-mcp, and uv's console script is a #!/bin/sh launcher. A POSIX shell resets PWD when it doesn't match the real working directory, so by the time Python started, PWD pointed at the plugin folder again.
3.3.0 starts Python directly:
uvx --from "gemini-faf-mcp>=3.2.1" python -I -X utf8 -m server
-
-I(isolated mode) matters: plainpython -m serverwould run aserver.pysitting in your project instead of ours. -
-X utf8:-Ialso ignoresPYTHONUTF8, so UTF-8 mode is turned on explicitly. -
>=3.2.1: an older installed copy without the fix is never used.
The tests passed because they launched the server directly. Installing the release the way a new user would is what caught it.
How we got it right
- After 3.2.1 shipped, we installed it as a new user would, and it didn't work in the project. That run is why 3.3.0 exists.
- The fix had two independent reviews and a re-check. The reviewers planted fake
server.pyfiles and older installed copies to try to break it. - 347 tests pass, 0 fail.
- After publishing, the plugin installed from GitHub with the real
agyfound the project'sproject.faf, wroteproject.fafandGEMINI.mdinto the project, and left its own folder untouched.
Not claimed
- Windows was not tried. If anybody wants to try it there, awesome.
- A server added by hand to Antigravity's
mcp_config.json(not the plugin) was not tried. - On an Intel Mac, the first start can take minutes: cryptography has had no Intel Mac wheel since 49.0, so it compiles once.
Try it
Antigravity CLI:
agy plugin install https://github.com/Wolfe-Jam/gemini-faf-mcp
Any other MCP client that runs a local server:
{ "mcpServers": { "gemini-faf": { "command": "uvx", "args": ["gemini-faf-mcp==3.3.0"] } } }
Claude Code:
claude mcp add gemini-faf-mcp -- uvx gemini-faf-mcp==3.3.0
Repo: https://github.com/Wolfe-Jam/gemini-faf-mcp · Release notes: https://github.com/Wolfe-Jam/gemini-faf-mcp/releases/tag/v3.3.0
Questions, nits, suggestions: comments welcome.
Originally published at faf.one.
Drafted by Claude · Approved by James Wolfe

Top comments (0)