Skip to main content
Glama
Oolab-labs

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to patchwork-os

No user-submitted related servers found.

    Related Servers

    • mcp-http-bridge

      cutlerbenjamin1-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      This server bridges a stdio MCP server to HTTP, allowing MCP clients that communicate over HTTP to use the server's tools. It includes a per-tool allow/deny filter for security.
      MIT

    • proxycept-mcp

      MoathOthman
      A
      license
      Not graded
      quality
      C
      maintenance
      A thin stdio-to-HTTP bridge that forwards MCP messages to the hosted Proxycept server, enabling stdio-only MCP clients to access Proxycept's tool catalog.
      9 npm
      MIT

    • MCP HTTP Proxy

      PintaAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes any stdio-based MCP server to the internet via HTTP/SSE transport, enabling remote agents to access MCP tools over a network.
      4 npm
      MIT

    • mcpmini

      AnswerDotAI
      A
      license
      Not graded
      quality
      A
      maintenance
      Minimal MCP server allowing Python functions to be served as MCP tools over stdio or HTTP, with a built-in client for connecting to MCP servers.
      105 PyPI
      2
      Apache 2.0

    • mcp-bridge

      Slothtron
      F
      license
      Not graded
      quality
      C
      maintenance
      A local stdio MCP server that bridges remote Streamable HTTP MCP servers to MCP clients, enabling transport normalization and optional outbound HTTP proxy support for restricted networks.
      -
    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

    B3.3/5.0

    Scored across 175 tools

    Disambiguation2/5

    With 175 tools, many have overlapping purposes (e.g., getHover, getHoverAtCursor, batchGetHover; runCommand, runInTerminal, sendTerminalCommand). Descriptions attempt to differentiate, but the sheer number increases the chance of agent misselection.

    Naming Consistency5/5

    All tool names follow a consistent camelCase verb_noun pattern (e.g., addLinearComment, searchAndReplace, fetchGithubIssue). No mixture of conventions detected.

    Tool Count1/5

    175 tools is far too many for any practical MCP server. This extreme count overwhelms agents and violates typical scoping expectations (3-15 tools ideal). The server tries to do everything, leading to bloat.

    Completeness4/5

    The tool set is remarkably broad, covering file editing, git, code analysis, debugging, testing, project management, AI tasks, and external integrations. Minor gaps exist (e.g., no direct PR merge tool), but overall coverage is impressive.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources