文件最后提交记录最后更新时间
feat(mcp): implement MCP client for external tool integration Add Model Context Protocol (MCP) client support to enable connecting to external MCP servers and using their tools through AtomCode's existing ToolRegistry. Changes: - Add mcp module with client, config, registry, and transports - Support stdio and HTTP transports for MCP servers - Load MCP config from project .mcp.json and user ~/.atomcode/mcp.json - Auto-register MCP tools with naming: mcp__{server}__{tool} - Add mcp-test-server binary for testing - Fix version check ordering in self_update.rs - Add comprehensive MCP documentation The implementation follows the Phase 1 MVP scope from the design doc, supporting tools/list and tools/call with proper timeout handling. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> 1 个月前
统一 ATOMCODE_HOME 路径语义:设置 ATOMCODE_HOME 后不再多加 .atomcode 这一级 13 天前
feat: support generic MCP OAuth 27 天前
feat: support generic MCP OAuth 27 天前
Auto-commit at turn #57 (9 files changed) 8 天前
feat(mcp): async server connection with dynamic tool registration - Add background MCP server connections to avoid blocking TUI startup - Display connection status (success/failure) in chat scrollback - Dynamically register MCP tools when servers connect via async ToolRegistry - Make ToolRegistry thread-safe with RwLock for concurrent access - Add McpConnectEvent enum for connection status notifications - Share tool registry via AgentHandle for dynamic registration Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> 1 个月前
feat(mcp): enhance daemon MCP reliability and protocol compliance - Auto-reload MCP registry when project directory changes via /cd - Add wait_for_initial_connections() to McpRegistry with Notify signal, so first chat request waits up to 5s for background MCP connections - HTTP transport: send notifications/initialized after initialize (MCP spec) - Add send_notification() method for fire-and-forget JSON-RPC notifications - Change daemon permission mode from DenyAll to BypassAll so MCP tools can actually execute (users implicitly authorize by configuring .mcp.json) - Add reconnect logic: if tools empty but servers configured, reload registry - Document stdio transport serialization limitation in .mcp.json.example 26 天前
chore(mcp): silence dead_code warning for wrap_cmd_script on non-Windows wrap_cmd_script's only non-test caller is gated by #[cfg(target_os = "windows")], so building on macOS/Linux produced a dead-code warning even though the function is still exercised by cross-platform tests. Gate the allow(dead_code) to non-Windows targets so Windows lib builds keep the lint and tests stay happy everywhere. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 20 天前
feat(mcp): implement MCP client for external tool integration Add Model Context Protocol (MCP) client support to enable connecting to external MCP servers and using their tools through AtomCode's existing ToolRegistry. Changes: - Add mcp module with client, config, registry, and transports - Support stdio and HTTP transports for MCP servers - Load MCP config from project .mcp.json and user ~/.atomcode/mcp.json - Auto-register MCP tools with naming: mcp__{server}__{tool} - Add mcp-test-server binary for testing - Fix version check ordering in self_update.rs - Add comprehensive MCP documentation The implementation follows the Phase 1 MVP scope from the design doc, supporting tools/list and tools/call with proper timeout handling. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> 1 个月前