Closed [AmmarClaw] Fix Gemini Tool Collision and Automate MCP Connection ID Storage

Fix Gemini Tool Collision and Automate MCP Connection ID Storage
By AmmarBasha2011
Assigned to

This PR addresses the Gemini duplicate tool declaration error by namespacing MCP tools and improves the user experience by automating the persistence of the GitHub Connection ID. Key changes: 1. **Tool Namespacing:** MCP tools are now prefixed with `mcp__` in the function declarations sent to Gemini. 2. **Tool Execution Update:** The `ToolRegistry` has been updated to strip the `mcp__` prefix before executing MCP tools, ensuring correct routing. 3. **Automated Environment Management:** A new `updateEnv` utility in `src/utils/env.ts` allows for programmatic updates to the `.env` file. 4. **Connection ID Persistence:** The `MCPService` now automatically saves the `GITHUB_CONNECTION_ID` to the `.env` file whenever a new connection ID is generated by Smithery, eliminating the need for manual configuration. 5. **User Notifications:** Telegram bot messages have been updated to reflect that the Connection ID is saved automatically. --- *PR created automatically by Jules for task [4989484905927716821](https://ift.tt/9aMX0kA) started by @AmmarBasha2011*

Labeled:

March 19, 2026 at 05:06PM
via GitHub https://ift.tt/YN3O4pC

Post a Comment

Previous Post Next Post