click2mcp
Related Servers
Alternatives to click2mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExposes any paparam CLI as an MCP server, automatically deriving tool definitions, resources, and prompts from the command's own schema, with validation before execution and support for both MCP protocol eras.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConverts any Python Click or Typer CLI into an MCP server automatically — zero-code transformation that introspects CLI commands and exposes them as MCP tools.9Apache 2.0
- AlicenseNot gradedqualityBmaintenanceTurns any command-line tool into an MCP server by parsing its --help, enabling AI assistants to discover and safely invoke CLI tools with validation, allow-listing, and sandboxing.MIT
- AlicenseNot gradedqualityCmaintenanceTurns any CLI command into an MCP server via a declarative YAML config, enabling safe, typed tool execution with no shell injection.MIT
- FlicenseCqualityDmaintenanceSchema-driven MCP server that exposes all Paperclip API operations as typed MCP tools over stdio or Streamable HTTP, supporting both authenticated and local_mode deployments.100-
- AlicenseNot gradedqualityDmaintenanceWrap any CLI as a Model Context Protocol (MCP) server for Claude, ChatGPT, Cursor, Gemini and any MCP-compatible client — schema auto-inferred from --help.50 npm13MIT
TDQS
Scored across 3 tools
demo_help and demo_run are clearly distinct (help vs execution), but `hello` has a useless description and could be mistaken for a test/echo or another command invocation. The boundary between hello and demo_run is unclear without knowing the CLI semantics.
Two tools follow a demo_* noun/verb pattern (demo_help, demo_run), but `hello` breaks the convention and has no domain prefix. The set is still readable, but the mixed style is noticeable.
Three tools is reasonable for a minimal CLI bridge: help, run, and a sample hello. The count is well-scoped, though `hello` feels like demo filler rather than a core operation.
For a CLI bridge, demo_help and demo_run together cover discovery and execution well. Minor gaps exist around structured output or error handling, but the core lifecycle is present.