One command to turn any CLI tool or REST API into an MCP server for Claude
mcp-x exposes only 2 meta-tools (list_tools, call_tool) that wrap arbitrary CLI/OpenAPI tools. The actual tool definitions are generated dynamically from CLI help text or OpenAPI specs and registered at runtime. While the server architecture is sound, the tool definitions themselves have critical gaps: parameter descriptions are generic ('Arguments to pass to the tool'), input schemas lack proper type constraints (all params default to string type), and error handling is minimal. The call_tool implementation catches FileNotFoundError and TimeoutExpired but returns unstructured text responses without guidance on recovery. No tool annotations (readOnlyHint, destructiveHint) are present. The list_tools handler correctly builds schemas from ToolDefinition objects, but the underlying ToolDefinition class (in parsers/cli.py and parsers/openapi.py, not shown) appears to generate overly simplistic parameter metadata.
Execute a registered tool by name with provided arguments
List all available tools registered with the MCP server
call_tool parameter 'arguments' lacks type constraints and description depth. Described as 'Arguments to pass to the tool' (generic); should specify expected structure, validation rules, and examples of valid argument patterns.
Error responses from call_tool are unstructured text (stdout + stderr concatenated). No error classification (retryable vs fatal), no recovery guidance. E.g., 'Error: command not found' gives LLM no actionable next step.
Generated parameter schemas (in list_tools handler) assign all parameters type 'string' without validation. No enums, patterns, min/max bounds, or format constraints. LLMs can pass invalid values (e.g., arbitrary strings for enum-like fields).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). call_tool can execute destructive commands (rm, delete, etc.) with no warning to the LLM that the operation is irreversible.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
call_tool does not validate that the tool name exists before attempting execution. Error handling is post-hoc ('unknown tool' check returns error text). No pre-flight validation or permission gating.