Menu
Configure and use ACECode's native MCP client for stdio, SSE, and Streamable HTTP MCP servers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Release ACECode from a user-provided version number. Use when Codex is asked to publish an ACECode version, update the Windows self-upgrade server, build and verify the updater package, commit release code, create an annotated Git version tag, or push release commits/tags.
说明 ACECode Desktop 原生桌面应用的用法，包括工作区、任务、会话、输入框、权限、可选 Git worktree、搜索、文件与差异面板、设置、技能、MCP、循环任务、通知、更新和故障排查。当用户询问 Windows、macOS 或 Linux 图形界面的操作方法时使用。不要用终端 TUI 的命令代替 Desktop 界面操作。
Explain how to use ACECode in a terminal, including the interactive TUI, headless prompt mode, sessions, worktrees, permission modes, keyboard controls, slash commands, skills, MCP, memory, and troubleshooting. Use when a user asks how to start, control, configure, or recover ACECode from a shell. Do not use for the native ACECode Desktop interface.
ACECode WebUI 的统一视觉规则 — 写设置 / 管理 / 配置 / 状态展示类页面或面板前必读。提炼自 SettingsPage 的「常规」「外观」section,覆盖容器、标题层级、卡片行、单选卡片、小型 input、状态指示、分隔线等。新 section 直接套这套 className,不要重新造视觉风格。
Use a saved model tagged with the vision capability to inspect images when the active model cannot reliably read image content.
ACECode WebUI 的统一视觉规则 — 写设置 / 管理 / 配置 / 状态展示类页面或面板前必读。提炼自 SettingsPage 的「常规」「外观」section,覆盖容器、标题层级、卡片行、单选卡片、小型 input、状态指示、分隔线等。新 section 直接套这套 className,不要重新造视觉风格。
| name | native-mcp |
| description | Configure and use ACECode's native MCP client for stdio, SSE, and Streamable HTTP MCP servers. |
| license | MIT |
| compatibility | ACECode native MCP client |
| metadata | {"source_id":"hermes-agent:mcp/native-mcp@4eecaf06e48834e105cbd989ae0bae5a2a618c1d","tags":["mcp","tools"]} |
Use this skill when the user wants to connect ACECode to MCP servers or understand how native MCP tools appear in the agent.
ACECode reads MCP server configuration from ~/.acecode/config.json under the mcp_servers object. It connects configured servers at startup and registers each discovered tool as:
mcp_<server_name>_<tool_name>
Server names are sanitized before they become part of tool names.
stdio: start a local MCP server process and communicate over stdin/stdout.sse: connect to an HTTP Server-Sent Events endpoint.http: use MCP Streamable HTTP with a single endpoint.{
"mcp_servers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "C:/Users/shao"]
},
"remote-search": {
"transport": "http",
"url": "https://mcp.example.com",
"sse_endpoint": "/mcp",
"headers": {
"X-Client": "acecode"
}
}
}
}
Restart ACECode after editing MCP configuration so startup can reconnect and register tools.
mcp_servers entry in ~/.acecode/config.json./mcp or /mcp list to inspect connection status and registered tools.mcp_<server>_<tool> tool name shown by ACECode.command, args, and required env values.url, sse_endpoint, headers, certificates, and auth token handling.