Skip to main content
Glama
veithly

mcp-server-wrapper

by veithly

Related Servers

Alternatives to mcp-server-wrapper

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables dynamic loading, hot-reloading, and orchestration of MCP servers without restarting Claude Code, allowing programmatic tool calling and workflow automation across multiple servers.
      2
      -
    • A
      license
      B
      quality
      A
      maintenance
      A meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.
      16
      112 PyPI
      144
      AGPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      A meta-MCP server that manages, aggregates, and proxies other MCP servers, letting LLMs search for, add, configure, enable, disable, and bundle servers at runtime. Tools from connected servers are exposed under unified prefixes, with persistent configuration and health monitoring.
      -
    • A
      license
      B
      quality
      D
      maintenance
      A meta-server that allows Claude to install other MCP servers from npm or PyPi, enabling easy expansion of Claude's capabilities with external tools.
      2
      110 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that builds itself by creating new tools as needed based on user requests (Requires restart of Claude Desktop to use newly created tools).
      4
      25
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      A meta MCP server that lets LLMs discover, add, configure, enable/disable, and aggregate other MCP servers at runtime, exposing their tools under unified prefixes. It persists configurations, reloads them dynamically, and provides health checks, kit management, and proxying so assistants can extend their own capabilities without human intervention.
      -

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: adding, listing, invoking, and removing servers or tools. There is no ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent pattern: mcp_<verb>_<object> (e.g., mcp_add_server, mcp_invoke, mcp_list_servers). The naming is predictable and uniform.

    Tool Count5/5

    With 5 tools, the set is well-scoped for managing MCP server configurations and tool invocation. It is neither too sparse nor too heavy.

    Completeness4/5

    The tools cover the core lifecycle: add, list, invoke, and remove. However, there is no update or get detailed server info, which may be a minor gap for maintenance tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues