Skip to main content
Glama

Related Servers

Alternatives to mcptoon

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables building and running zero-dependency MCP servers with automatic JSON Schema generation, exposing Python tools to Claude Desktop, Cursor, and autonomous agent fleets.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Automatically 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      This 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.
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Turn 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.
      3
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      5 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool has a describable job and the descriptions cross-reference each other (manifest→inspect→call, skills→resolve_skills, index→search→retrieve), which makes the intended chains clear. The weak spot is the meta/status cluster: health, servers, session and usage are all 'report something about the gateway', and an agent may briefly hesitate between health and servers or between session and usage.

    Naming Consistency4/5

    Every tool shares the same mcptoon_ namespace prefix and snake_case, so the set reads as one family. The trailing segment mixes verbs (call, inspect, retrieve, resolve_skills) with bare nouns (manifest, session, health, servers, skills, usage), so there is no strict verb_noun grammar, but it is predictable and readable.

    Tool Count5/5

    Twelve tools is squarely in the sweet spot for a gateway. Each one maps to a distinct need — discover, introspect, invoke, decompress, index, search, skills, and observability — and none looks like filler.

    Completeness4/5

    The invoke path (servers→manifest→inspect→call→retrieve) and the skills path are fully covered, with health and usage for diagnostics. The knowledge-base path is the gap: you can index and search, but there is no way to list what is indexed, delete or re-index a stale document, so an agent can create state it cannot clean up.

    Maintenance

    ActivityActive
    ResponsivenessResponsive