mcptoon
Related Servers
Alternatives to mcptoon
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables building and running zero-dependency MCP servers with automatic JSON Schema generation, exposing Python tools to Claude Desktop, Cursor, and autonomous agent fleets.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAutomatically converts any CLI built with Python's Typer into an MCP server without changing code. Gives AI agents instant access to thousands of CLI tools.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceThis MCP server is a zero-config CLI tool that lets developers tap into any stdio-based MCP server from their terminal, enabling them to list tools/resources/prompts, call tools with JSON arguments, and health-check servers without requiring a full AI client or browser setup.1MIT
- AlicenseCqualityDmaintenanceTurn any REST API into an MCP server in one command. Point mcpify at an OpenAPI spec and every endpoint becomes a tool your AI agent (Claude, Cursor, Windsurf) can call — zero glue code, always in sync with the spec.35MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that publishes CLI tools on your machine for discoverability by LLMs7 npm1MIT
TDQS
Scored across 9 tools
Most tools target clearly distinct operations: manifest lists tools, inspect shows a schema, call runs one, retrieve decompresses output, and skills/resolve_skills are separate (list vs. rank). There is mild overlap between health, servers, and usage (all report gateway state), but descriptions draw usable boundaries.
Every tool uses the same mcptoon_ snake_case prefix, which is highly consistent. The suffixes mix single-word nouns (health, manifest, servers, skills, usage) with verbs (retrieve, call, inspect) plus resolve_skills, so it's predictable but not a strict verb_noun pattern.
Nine tools is well-scoped for a gateway that must expose discovery, schema inspection, invocation, decompression, and diagnostics. Each tool earns its place with no redundancy.
The surface covers the full gateway lifecycle: discover servers (servers), list tools (manifest), inspect schemas (inspect), invoke (call), decompress (retrieve), plus skills and usage diagnostics. A keyword search over tools (distinct from skills resolution) is the only noticeable gap.