In my earlier post Gemini CLI and Tinderbox I’ve mentioned that Google is going full throttle into Antigravity 2.0 AI tool suite which will eventually replace gemini-cli.
Now there are some issues with that, since their new CLI called agy is agentic-first and if I copy the config from gemini-cli to just launch Tinderbox, it will detect and launch Tinderbox MCP, but blow it up after user writes a prompt of any kind. Actually agy tries so hard to achieve the user’s goal as it fallbacks to osascript invocation which isn’t what we want…
In order to fix that I’ve actually vibe-coded the solution in Gemini Web itself, although it’s quite a low-level pythonic approach which requires pip to install fastapi and uvicorn packages. Tested with Python 3.14
The code for that I have committed to my own little garbag-ish repo on BitBucket as tinderbox-mcp-net.py
For those who actually use agy and want it configured for this solution, please make a .agents/mcp_config.json file in your project’s root and paste that:
{
"mcpServers": {
"tinderbox": {
"url": "http://localhost:8080”
}
}
}
Then launch my script which will launch Tinderbox with a networking bridge and finally launch agy and detect tinderbox MCP via /mcp (should detect the tools and we’re set for happy prompting)
I was slightly inspired by the works of Daniel Tubb called Fichero Toolbox, which author also admitted as vibe coded (kudos for being sincere) but his approach went a little too far in macOS plumbing, by playing with services and triggering a couple of security prompts; nothing that I expect on my daily driver box 
As for vibe coding it is quite fun, but will always require some IT generalist knowledge to address the issues that come along. In this case I had only three (how MCP inits, how lines are handled from Tinderbox and that I had to chose python instead of the initial naive bash solution with socat, lol).