[Bug]: MCP integration not working - AionUi bypasses Gemini CLI MCP servers and uses direct API calls

[Foadsf]

Platform

Windows

AionUi Version

1.2.2

Bug Description

AionUi appears to bypass the configured Gemini CLI MCP servers and instead uses direct API calls and built-in functions. This prevents users from leveraging properly configured MCP servers for enhanced functionality.

Key Issues Observed:

1. Git operations use direct git commands instead of MCP git server
2. File system operations fail with security restrictions instead of using MCP filesystem server
3. Web searches use direct Google API instead of configured MCP brave-search server
4. No evidence of MCP tool calls in debug output despite properly configured MCP servers in Gemini CLI

Steps to Reproduce

1. Configure MCP servers in %USERPROFILE%\.gemini\settings.json with working filesystem, git, and brave-search servers
2. Verify MCP servers work in standalone Gemini CLI using /mcp list command
3. Start AionUi with npm start
4. Select Gemini agent and ask: "Can you check the git status of this project?"
5. Observe that AionUi uses direct git commands instead of MCP git server
6. Ask: "Show me files in the C:\path\to\folder directory"
7. Observe security restriction error instead of MCP filesystem access
8. Ask: "Search for nodejs tutorials"
9. Observe direct Google search instead of MCP brave-search server

Expected Behavior

AionUi should leverage the user's configured Gemini CLI MCP servers to provide enhanced functionality including:

• Git operations through MCP git server
• File system access through MCP filesystem server
• Web searches through configured MCP search servers
• Display of MCP tool usage in conversations

Actual Behavior

AionUi bypasses MCP integration entirely and uses:

• Direct shell git commands
• Built-in file system restrictions that block access
• Direct Google API calls for searches
• No MCP tool call indicators in debug output

Debug Evidence:

• No MCP server initialization messages in AionUi logs
• Direct API calls shown: geminiTools.done.request with oauth-personal gemini-2.5-flash
• Error: ReadFolder ("path":"C:\\dev") Path must be within one of the workspace directories

Additional Context

Secondary Bug: Settings dialog crashes when "Cancel" is pressed, showing "Uncaught runtime errors" requiring application restart.

MCP Configuration Verified Working:

• Gemini CLI standalone shows: 🟢 filesystem (14 tools), 🟢 git (13 tools), 🟢 brave-search (2 tools)
• All MCP servers respond correctly when used directly through Gemini CLI
• Settings file: %USERPROFILE%\.gemini\settings.json properly configured

Architecture Issue:
AionUi appears to use direct Gemini API integration rather than leveraging the Gemini CLI as a backend process, which prevents MCP server utilization.

[aionui]

🤖 Hi @Foadsf, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[joreyolo]

me too.

[aionui]

🤖 Hi @kuishou68, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[aionui]

🤖 I'm sorry @kuishou68, but I was unable to process your request. Please see the logs for more details.