Updates and Agent Integration
App Updates
- Click the version entry at the top of the main screen to open the update panel.
- Click
Check for Updatesin the panel. - If a new version is found, the panel shows the version comparison and release summary.
- Review the release notes, then click
Apply Update. - Wait for the update to finish and the app to restart.
Script Run Settings
In System Settings → Script Run, you can control:
- whether
XXTLanControl.luais uploaded before running scripts - whether it is also uploaded when running
<Selected on Device> - whether it is uploaded during bulk script upload to devices
- whether existing
XXTLanControl.luafiles insideScript Directoryshould be updated to the version bundled in the current control center
Skill Install Panel
Choose xxtlancontrol for control-center operations or xxtouch-script for XXT/XPP projects and XXTouch Lua script development. Install, update, remove, or download each Skill separately in the Skill Install panel. Claude Desktop and 3p import the selected ZIP through Customize > Skills > + > Create skill > Upload a skill and manage it in Claude.
Use Install, Update, or Uninstall in the target agent’s row, or choose Download ZIP for manual installation.
Agents can also read either Skill and its references through MCP. Local scripts and project templates require the complete Skill package.
MCP Install Panel
In System settings → MCP Install, install or remove MCP for the agents you use. Supported targets:
- Claude Code
- Codex
- Claude Desktop
- Claude Desktop 3p
- VS Code
- GitHub Copilot
- Cursor
- Devin Desktop/CLI
- Antigravity
- Trae
- TRAE CN
- TRAE SOLO
- Qoder IDE
- Qoder Desktop/CLI
- Qoder CN IDE
- Qoder CN Desktop/CLI
- CodeBuddy
- WorkBuddy
- WorkBuddy AI
WorkBuddy and WorkBuddy AI are installed, detected, and uninstalled independently. WorkBuddy AI uses ~/.workbuddy-ai/mcp.json for user-level MCP configuration (%USERPROFILE%\.workbuddy-ai\mcp.json on Windows); WorkBuddy continues to use ~/.workbuddy/mcp.json.
On-demand Capabilities and Skills
MCP tools provide public entrypoints, and business operations are called through tool_call. Call directly when the name and parameters are known.
Target Control Center Address and Snippets
- By default, MCP installation points to the current XXTLanControl
/mcpURL. - If you want the agent to connect to another control center, enter that target address in the panel and it will generate the matching
/mcpURL. - All currently listed installation targets support HTTP integration.
- For agents that are not shown in the target list, you can copy the JSON or TOML HTTP snippets shown in the panel.
- Claude Desktop and Claude Desktop 3p connect to the current
/mcpURL through the localnpx -y mcp-remote@latestbridge. Node.js and npx must be available locally, and Claude Desktop must be fully restarted after the configuration is written so it reloads MCP. - Claude Desktop usually stores its configuration at
~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS or%APPDATA%\Claude\claude_desktop_config.jsonon Windows. Claude Desktop 3p uses a separate directory:~/Library/Application Support/Claude-3p/claude_desktop_config.jsonon macOS, and currently%LOCALAPPDATA%\Claude-3p\claude_desktop_config.jsonon Windows. - When troubleshooting Claude Desktop MCP connections, standard-mode logs are under
~/Library/Logs/Claudeon macOS or%APPDATA%\Claude\logson Windows. Claude Desktop 3p logs are under~/Library/Logs/Claude-3pon macOS and currently under%LOCALAPPDATA%\Claude-3pon Windows.
Before You Use It
- The backend
/mcpendpoint does not require an access key by default. Any agent that can reach the backend port can connect. - If you no longer need agent integration later, it is a good idea to remove it from the same panel first.