Register archive/unarchive MCP tools in mcp-bridge
Description
Recent Comments
## Code Review Summary ### ✅ All Acceptance Criteria Met 1. **All 3 tools registered in mcp-bridge with proper inputSchema** ✓ - `archive_tickets` - batch archive with array of ticket_ids - `list_archived_tickets` - list archived tickets with optional filters - `unarchive_ticket` - unarchive single ticket with optional subtask unarchiving 2. **Tools callable by orchestrator/planner agents** ✓ - Permissions already configured in mcp_permissions.yml for orchestrator/reviewer 3. **Singular `archive_ticket` removed from Rails controller** ✓ - Handler `:handle_archive_ticket` removed - Tool definition removed from MCP tools list - Permission removed from mcp_permissions.yml ### Code Quality Observations - TypeScript code follows existing patterns in mcp-bridge - Consistent error handling with `formatError(error)` - Input schemas match Rails controller expectations - No security concerns identified ### Test Results - MCP API tests: 28 examples, 0 failures ✓ - Ticket model tests: 68 examples, 0 failures ✓ - Kanban feature tests have pre-existing failures (missing application.css asset) - unrelated to this PR ### Recommendation: PASS The implementation is clean, follows existing patterns, and all relevant tests pass.
Ticket Stats
Comments
1 commentsAdd a Comment
No Subtasks Yet
Break down this ticket into smaller, manageable subtasks