Skip to main content
Glama

Related Servers

Alternatives to wasmagent-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight and fast MCP server that enables AI agents to efficiently discover and execute tools through progressive disclosure, minimizing context consumption while supporting safe code execution in external environments.
      13 npm
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to accomplish multi-step work by writing a single sandboxed JavaScript program that drives shell, filesystem, HTTP, and every tool of any configured MCP server, returning only a small summary instead of raw JSON. This collapses dozens of advertised tool schemas into one tool, cutting per-request context by roughly 26× while keeping disabled upstream servers reachable.
      1
      47 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Universal MCP server for executing TypeScript and Python code with progressive disclosure, reducing token usage by 98% by enabling on-demand access to all other MCP tools through code execution rather than loading tool definitions directly.
      38 npm
      130
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates many upstream MCP servers behind a single proxy so AI coding editors can access hundreds of tools without hitting tool-count limits, while trimming tool schemas to cut prompt token usage by up to ~98%. It also sandboxes tool calls by blocking path traversal, dangerous shell chaining, and host environment variable leakage.
      PolyForm Noncommercial 1.0.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables building safe, programmable Code Mode MCP servers from upstream tool sources, with model-authored TypeScript running in a sandbox and tool calls routed to trusted host-side providers.
      1
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: docs_search for discovering downstream tools, and execute_code for running code that calls them. There is no overlap or confusion.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern with snake_case: docs_search and execute_code.

    Tool Count5/5

    Two tools is exactly right for this server's purpose as a meta-agent: search to discover, execute to run. It's minimal but complete.

    Completeness5/5

    The tool surface fully covers the intended workflow: discovering available downstream tools and executing code that chains them. There are no obvious gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues