cli

var CurrentVersion string

var ExecCmd = &ucli.Command{
	Name:      "exec",
	Usage:     "Execute JavaScript code to orchestrate multiple MCP tool calls",
	ArgsUsage: "<code | ->",
	Description: `Execute JavaScript code that can call multiple MCP tools with logic.

Use this when you need to:
- Chain multiple tool calls
- Process data between calls
- Use conditionals or loops
- Aggregate results

For single tool calls, use 'invoke' instead.

The 'mcp.callTool(name, params)' function is available to call tools.
Tool names can be in either format:
  - JS name (camelCase): githubSearchRepos
  - Original name: github__search_repos

Examples:
  # Chain tool calls (config mode)
  mh exec -c config.json 'const user = mcp.callTool("dbGetUser", {id: 1}); mcp.callTool("emailSend", {to: user.email})'

  # Read code from stdin
  cat script.js | mh exec -c config.json -

  # With remote server (use tool names directly)
  mh exec -u http://localhost:3000 'const a = mcp.callTool("add", {x: 1, y: 2}); mcp.callTool("multiply", {x: a, y: 3})'

  # With stdio server (use tool names directly)
  mh exec --stdio 'mcp.callTool("echo", {message: "hello"})' -- npx @modelcontextprotocol/server-everything

  # JSON output
  mh exec -c config.json --json 'mcp.callTool("githubListRepos", {})'`,
	Flags:  MCPClientFlags(),
	Before: ValidateMCPClientFlags,
	Action: runExec,
}

var InspectCmd = &ucli.Command{
	Name:      "inspect",
	Usage:     "Inspect a tool from an MCP service",
	ArgsUsage: "<tool-name>",
	Description: `Show detailed information about a specific tool from an MCP service.

Provide --url (-u) for a remote MCP service, --config (-c) to load local
stdio/http/sse servers from config, or --stdio to spawn a subprocess.
Takes tool name as a required positional argument.

Tool names can be in either format:
  - JS name (camelCase): githubSearchRepos
  - Original name: github__search_repos

Examples:
  # Inspect a tool
  mh inspect -u http://localhost:3000 myTool

  # Inspect a tool with JSON output
  mh inspect -u http://localhost:3000 myTool --json

  # Inspect a tool using SSE transport
  mh inspect -u http://localhost:3000 -t sse myTool

  # Inspect a tool from config (stdio/http/sse)
  mh inspect -c config.json githubSearchRepos

  # Inspect a tool from a stdio MCP server
  mh inspect --stdio echo -- npx @modelcontextprotocol/server-everything`,
	Flags:  MCPClientFlags(),
	Before: ValidateMCPClientFlags,
	Action: runInspect,
}

var InvokeCmd = &ucli.Command{
	Name:      "invoke",
	Usage:     "Invoke a tool on an MCP service",
	ArgsUsage: "<tool-name> [params-json | -]",
	Description: `Invoke a tool on an MCP service with optional JSON parameters.

Provide --url (-u) for a remote MCP service, --config (-c) to load local
stdio/http/sse servers from config, or --stdio to spawn a subprocess.
Takes tool name as a required positional argument.
Parameters can be provided as:
  - A JSON string argument
  - "-" to read JSON from stdin
  - Omitted for tools with no required parameters

Tool names can be in either format:
  - JS name (camelCase): githubSearchRepos
  - Original name: github__search_repos

Examples:
  # Invoke a tool with no parameters
  mh invoke -u http://localhost:3000 myTool

  # Invoke a tool with JSON parameters
  mh invoke -u http://localhost:3000 myTool '{"key": "value"}'

  # Invoke a tool with parameters from stdin
  echo '{"key": "value"}' | mh invoke -u http://localhost:3000 myTool -

  # Invoke a tool with JSON output
  mh invoke -u http://localhost:3000 myTool '{"key": "value"}' --json

  # Invoke a tool from config (stdio/http/sse)
  mh invoke -c config.json githubSearchRepos '{"query": "mcp"}'

  # Invoke a tool from a stdio MCP server
  mh invoke --stdio echo '{"message": "hello"}' -- npx @modelcontextprotocol/server-everything`,
	Flags:  MCPClientFlags(),
	Before: ValidateMCPClientFlags,
	Action: runInvoke,
}

var ListCmd = &ucli.Command{
	Name:  "list",
	Usage: "List tools from an MCP service",
	Description: `List all available tools from an MCP service.

Provide --url (-u) for a remote MCP service, --config (-c) to load local
stdio/http/sse servers from config, or --stdio to spawn a subprocess.

Examples:
  # List tools from a remote server
  mh list -u http://localhost:3000

  # List tools with JSON output
  mh list -u http://localhost:3000 --json

  # List tools using SSE transport
  mh list -u http://localhost:3000 -t sse

  # List tools from config (stdio/http/sse)
  mh list -c config.json

  # List tools filtered by server
  mh list -c config.json --server github

  # List tools filtered by keywords
  mh list -c config.json --query "search,file"

  # List tools from a stdio MCP server
  mh list --stdio -- npx @modelcontextprotocol/server-everything`,
	Flags: append(MCPClientFlags(),
		&ucli.StringFlag{
			Name:  "server",
			Usage: "filter tools by server name",
		},
		&ucli.StringFlag{
			Name:  "query",
			Usage: "comma-separated keywords for search (matches name or description)",
		},
	),
	Before: ValidateMCPClientFlags,
	Action: runList,
}

var ServeCmd = &ucli.Command{
	Name:  "serve",
	Usage: "Start the MCP hub server",
	Description: `Start the MCP hub server with the specified transport.

Transport Types:
  stdio  - Standard input/output (default, for CLI integration)
  http   - HTTP server with StreamableHTTP protocol
  sse    - HTTP server with Server-Sent Events protocol

Examples:
  # Run with stdio transport (default)
  mh serve -c config.json

  # Run with HTTP transport on port 8080
  mh serve -c config.json -t http -p 8080

  # Run with SSE transport on custom host and port
  mh serve -c config.json -t sse --host 0.0.0.0 -p 3000

  # Run with verbose logging
  mh serve -c config.json --verbose`,
	Flags:  MCPServeFlags(),
	Action: runServe,
}

var SkillsCmd = &ucli.Command{
	Name:  "skills",
	Usage: "Discover and install agent skills",
	Description: `Search and install skills from the open agent skills ecosystem.

Skills are modular packages that extend agent capabilities with specialized
knowledge, workflows, and tools.

Examples:
  # Search for skills
  mh skills find react
  mh skills find "pr review"

  # Install a skill
  mh skills add vercel-labs/agent-skills@react-best-practices`,
	Commands: []*ucli.Command{
		skillsFindCmd,
		skillsAddCmd,
	},
}

var UpdateCmd = &ucli.Command{
	Name:  "update",
	Usage: "Update mh to the latest version",
	Description: `Check for updates and upgrade mh to the latest version.

Examples:
  # Check and update to latest
  mh update

  # Check only (dry run)
  mh update --check`,
	Flags: []ucli.Flag{
		&ucli.BoolFlag{
			Name:  "check",
			Usage: "only check for updates, don't install",
		},
	},
	Action: runUpdate,
}