Skip to main content
Glama

Related Servers

Alternatives to mcp-everything

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Lets your AI find the open-source tool it needs on GitHub and install it as an MCP tool, in a sandbox, after you approve. Reads only the folders you grant; no network unless allowed.
      5
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Finds MCP servers in the MCP Rating index and connects to them on demand, proxying their tools under namespaced names and notifying the client when tools change. Each server gets a short environment allowlist plus only the variables you name for it, so other API keys in your environment aren't passed on. Files aren't isolated unless you opt into Docker containers.
      13
      425 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Dynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).
      8
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP servers that wrap developer tools like git, npm, Docker, and test runners, returning schema-validated, token-efficient JSON so agents can use structured data directly.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.
      MIT

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct operations along a coherent lifecycle (search → install → inspect → invoke → configure → uninstall). The only mild overlap is among the three tool-generation paths — install_project, discover_tools, and connect_mcp_server — which a newcomer could briefly confuse, though their descriptions differentiate them well.

    Naming Consistency4/5

    The dominant pattern is verb_noun (search_projects, install_project, call_project_tool, connect_mcp_server, uninstall_project). The sandbox tools use a resource-prefix form (sandbox_exec, sandbox_read_file, sandbox_write_file) and project_info is noun-only, but all are readable and predictable within their group.

    Tool Count5/5

    15 tools sit at the top of the ideal range and each earns its place: search, install, inspect, invoke, publish/select, sandbox I/O, network, discovery, MCP server management, and removal are all distinct capabilities. Nothing feels redundant or padded.

    Completeness4/5

    The surface covers the full project lifecycle, including sandbox file I/O, network control, and MCP server registration/teardown. Minor gaps remain: there is no in-place update/reinstall (must uninstall then install), and no way to list or delete files inside a sandbox.