Skip to content

fix: remove Antigravity MCP registration on uninstall#44

Open
ahmedabdelkarim504-commits wants to merge 1 commit into
monk-io:mainfrom
ahmedabdelkarim504-commits:fix/uninstall-cleanup-mcp
Open

fix: remove Antigravity MCP registration on uninstall#44
ahmedabdelkarim504-commits wants to merge 1 commit into
monk-io:mainfrom
ahmedabdelkarim504-commits:fix/uninstall-cleanup-mcp

Conversation

@ahmedabdelkarim504-commits

Copy link
Copy Markdown

What this does

Adds MCP config cleanup to the uninstaller, removing the \mcpServers.monk\ entry from ~/.gemini/config/mcp_config.json\ when present.

Problem

The uninstaller removed the companion binary and agent data but left the \mcpServers.monk\ entry in Antigravity's global config. This caused Antigravity to expose a dead Monk MCP entry after uninstall, potentially showing connection failures.

How it works

Adds
emove_antigravity_mcp()\ which uses jq (or Python fallback) to delete the \monk\ key from \mcpServers, then cleans up the empty \mcpServers\ object if no other entries remain. Called before the final completion message.

Testing

Verified with the reproduction script from the issue — after uninstall, the config no longer contains the \monk\ entry while other MCP servers are preserved.

Fixes #27

The uninstaller removed the companion binary and agent data but left
the mcpServers.monk entry in ~/.gemini/config/mcp_config.json. This
could cause Antigravity to expose a dead Monk MCP entry after uninstall.

Adds remove_antigravity_mcp() which cleans up the registration using
jq or the Python fallback, matching the pattern in register_antigravity_mcp().

Fixes monk-io#27
@ahmedabdelkarim504-commits

Copy link
Copy Markdown
Author

/claim Fixes #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug bounty] official uninstall leaves Antigravity MCP registration active

2 participants