Skip to main content
Glama
veithly

mcp-server-wrapper

by veithly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-wrapper

No user-submitted related servers found.

    Related Servers

    • MCP Proxy

      lizTheDeveloper
      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
      -

    • Magg

      sitbon
      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
      66 PyPI
      143
      AGPL 3.0

    • MCP Installer

      ZNCOU
      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
      137 npm
      1
      MIT

    • mcp-tool-builder

      hanweg
      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
      -
    • Fastn Server by fastn-ai

      Fastn Serverofficial

      fastn-ai
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables dynamic tool registration and execution based on API definitions, providing seamless integration with services like Claude.ai and Cursor.ai.
      23
      MIT

    • mcpgo

      jschoemaker
      A
      license
      A
      quality
      D
      maintenance
      Enables managing other MCP servers from within Claude Code, including wrapping for reliable restarts, listing, adding, removing, and checking health.
      11
      52 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources