Chris Hendrickson
7b83572f7a
- Add DewToolCommand mixin that auto-derives MCP tool JSON Schema from ArgParser, eliminating the need to define CLI commands and MCP tools separately - Add schemaFromArgParser() to generate JSON Schema from ArgParser options - Add CommandRegistry.mcpTools recursive collector for all DewToolCommand subcommands - Refactor all kanban subcommands to use the mixin; switch get/update/delete from positional rest args to --id / -i option for schema compatibility - Promote list to a proper CLI subcommand (was MCP-only before) - Add search, comment, and config subcommands (CLI + MCP tools) - Add TicketStore.addComment() for non-destructive comment appending - Simplify mcp.registerCommands() to take only CommandRegistry - Simplify CLI entry point (no more KanbanToolProvider/McpToolRegistry) - Delete stale files: kanban_tool_provider.dart, mcp_tool_provider.dart, mcp_tool_registry.dart (superseded by DewToolCommand mixin) - Add tools/mcp_client.dart debug client for manual MCP server testing - Update .vscode/mcp.json with correct server config All 26 tests pass, dart analyze clean. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
15 lines
488 B
Dart
15 lines
488 B
Dart
library;
|
|
|
|
export 'src/dew_mcp_base.dart';
|
|
|
|
import 'package:dew_core/dew_core.dart';
|
|
import 'package:dew_mcp/src/dew_mcp_base.dart';
|
|
|
|
/// Registers the MCP command into [commandRegistry].
|
|
///
|
|
/// Tools are resolved lazily from [commandRegistry.mcpTools] when the server
|
|
/// starts, so all feature packages must call their own [registerCommands]
|
|
/// before this is invoked.
|
|
void registerCommands(CommandRegistry commandRegistry) {
|
|
commandRegistry.register(McpCommand(commandRegistry));
|
|
}
|