Skip to main content
Glama
tmustier

pi-code-mode-mcp

by tmustier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pi-code-mode-mcp

No user-submitted related servers found.

    Related Servers

    • programmatic-mcp

      alesya-h
      A
      license
      Not graded
      quality
      D
      maintenance
      A meta MCP server that orchestrates other MCP servers by lazily connecting to them and exposing their tools as JavaScript libraries. It allows users to execute JavaScript code that programmatically interacts with multiple MCP servers within a unified environment.
      12 npm
      1
      MIT

    • dynamic-mcp

      mcpland
      A
      license
      B
      quality
      C
      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

    • MCPMan

      semistrict
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server manager that acts as a proxy/multiplexer, enabling connections to multiple MCP servers simultaneously and providing JavaScript code execution with access to all connected MCP tools. Supports both stdio and HTTP transports with OAuth authentication, batch tool invocation, and dynamic server management.
      5 npm
      MIT

    • pi-codemode-mcp

      mitsuhiko
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP extension that allows coding agents to manage and compose MCP tools by executing JavaScript in a sandboxed environment. It features tools for listing available MCP capabilities and a management command for handling authentication and tool policies.
      37
      -

    • proxy-mcp

      Rixmerz
      F
      license
      A
      quality
      D
      maintenance
      Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.
      7
      -
    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.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion or overlap between tools. The agent can only use 'exec', making disambiguation trivial.

    Naming Consistency5/5

    With only one tool named 'exec', naming is perfectly consistent. The tool name is a straightforward verb, aligning with common conventions for action-oriented tools.

    Tool Count4/5

    The single tool 'exec' serves as a meta-orchestrator that can run arbitrary JavaScript to discover and compose other MCP tools. While unconventional, this design is intentional and scoped to its purpose. The count is minimal but arguably appropriate for a tool that replaces many specific ones.

    Completeness4/5

    The 'exec' tool provides a comprehensive environment to search, describe, and invoke any MCP tool, making it complete for its intended role as a discovery and composition layer. However, it lacks dedicated tools for specific operations, relying on programming logic, which may be considered a gap for agents that cannot write code.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources