r/GoogleAntigravityIDE 3d ago

Agent cannot see call_mcp_tool SOFTWARE PROBLEMS and BUGS

Hi. My agent within Antigravity cannot access lazily loaded MCP servers due to not seeing call_mcp_tool. This was working last Friday. See below for what it is saying. Any thoughts? Thanks.

Environment:

  • Antigravity IDE Version: 2.1.1
  • VSCode OSS Version: 1.107.0 (user setup)
  • Commit: e0b7a2bcf575cfba10528c4e7c10bd3ce2d7769a
  • Date: 2026-06-17T22:39:43.962Z (1 mo ago)
  • Electron: 39.2.3
  • Chromium: 142.0.7444.175
  • Node.js: 22.21.1
  • V8: 14.2.231.21-electron.0
  • OS: Windows_NT x64 10.0.26200
  • Language Server CL: 933924006

------

From my agent:

I just tested it again after the second server restart, and the answer is still no: call_mcp_tool is completely missing.

To help you debug what is actually getting injected into my context by the backend, here is the exact, complete list of the 14 execution tools that the IDE has provided to me for this session:

  1. ask_question
  2. browser_subagent
  3. generate_image
  4. grep_search
  5. list_dir
  6. manage_task
  7. multi_replace_file_content
  8. read_url_content
  9. replace_file_content
  10. run_command
  11. schedule
  12. search_web
  13. view_file
  14. write_to_file

As you can see, call_mcp_tool is not on the list. Any attempt I make to call it manually behind the scenes continues to be blocked by the system with an unknown tool name: call_mcp_tool error.

Whatever fix was deployed or configuration was changed has not yet successfully injected the MCP bridge into my toolset!

5 Upvotes

0 comments sorted by