feat(mcp): migrate backend from Hermes to LibreChat

[itsablabla]

Summary

Replaces the custom Hermes Agent backend with LibreChat as the headless API backend. LibreChat provides native MCP support (118 Nextcloud tools via Streamable HTTP), multi-model switching, built-in context compression, and an agent framework — eliminating the custom agent loop, context overflow bugs, and per-tool middleware that required constant patching.

What changed

PHP Proxy (OpenClawService.php + AgentController.php)

• Default URL: http://localhost:18789 (Hermes) → http://LibreChat:3080 (Docker DNS on nextcloud-aio network)
• API path: /v1/chat/completions → /api/agents/v1/chat/completions (LibreChat's OpenAI-compatible agents endpoint)
• Model: hermes-agent → agent_jada_nextcloud (LibreChat agent configured with Gemini 2.5 Flash + 118 MCP tools)
• Health endpoint now queries LibreChat's /api/agents/v1/models and reports engine: librechat

Vue Frontend (ChatView.vue)

• Added handling for standard OpenAI delta.tool_calls format (LibreChat sends tool calls this way instead of Hermes's custom event: hermes.tool.progress)
• Tool names stripped of _mcp_serverName suffix for display (e.g., nc_webdav_list_directory_mcp_nextcloud → nc_webdav_list_directory)
• Backward compat: legacy Hermes hermes.tool.progress events still parsed

Metadata

• Version bumped to 0.4.0
• info.xml description updated to reflect LibreChat architecture

Infrastructure (already deployed on server)

• LibreChat Docker stack (5 containers) running on 83.228.213.100
• LibreChat connected to nextcloud-aio Docker network (DNS name: LibreChat)
• Agent agent_jada_nextcloud created in MongoDB with sys__all__sys_mcp_nextcloud (all 118 tools)
• Nextcloud MCP server connected via http://nextcloud-mcp-server:8000/mcp (Streamable HTTP)
• iptables MASQUERADE rule for librechat_default network (external API access)

Review & Testing Checklist for Human

• Send a chat message in https://next.garzaos.online/apps/jadaagent/ and verify streaming response works
• Trigger a tool call — ask "List my Nextcloud files" and verify the tool call appears in the right panel with the correct name (not the raw _mcp_nextcloud suffix)
• Verify health display — footer should show "Gemini (via LibreChat) · 118 tools" and greeting should show "118 tools across 1 servers"
• Check mobile — ensure chat input remains visible on iOS Safari during streaming (regression check from v0.2.6 fix)
• Verify conversation persistence — send a message, reload the page, confirm the conversation + response survived

Notes

• The LibreChat API key is stored in Nextcloud's app config (openclaw_token), not hardcoded in PHP
• LibreChat's tool name format is toolName_mcp_serverName (server name LAST, not first) — this was the root cause of the MCP tool parsing bug in the previous session
• The sys__all__sys_mcp_nextcloud tool reference tells LibreChat to load ALL tools from the nextcloud MCP server, instead of listing each of the 118 tools individually
• Hermes container is still running but no longer used by Jada Agent — can be stopped after verifying LibreChat works

Link to Devin session: https://app.devin.ai/sessions/f4e16f12bfa34fc6bdc3d73a833a5d91
Requested by: @itsablabla

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring