patchwork-os
Related Servers
Alternatives to patchwork-os
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis 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
- AlicenseNot gradedqualityCmaintenanceA bridge server that converts stdio protocol to streamable-http protocol, allowing clients to interact with MCP services over HTTP.2Mulan Permissive Software , Version 2
- AlicenseNot gradedqualityCmaintenanceA 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.7 npmMIT
- AlicenseCqualityBmaintenanceEnables MCP clients to interact with OpenCode 2.x/3.x servers through direct /api/... HTTP routing and ~85 tools spanning sessions, messages, files, config, providers, projects, input, TUI, and workflows. Runs as a zero-dependency, pure-JavaScript stdio bridge with no SDK or build step.85MIT
- AlicenseNot gradedqualityDmaintenanceExposes any stdio-based MCP server to the internet via HTTP/SSE transport, enabling remote agents to access MCP tools over a network.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceMinimal 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.76 PyPI2Apache 2.0
TDQS
Scored across 178 tools
Several tool families overlap heavily: hover has getHover, getHoverAtCursor, getTypeSignature, and batchGetHover; navigation has goToDefinition, batchGoToDefinition, and navigateToSymbolByName; execution has runCommand, runInTerminal, and sendTerminalCommand. Descriptions add detail, but across 178 tools the boundaries remain fuzzy enough to cause frequent misselection.
Names are consistently camelCase, but the set mixes verb_noun (getGitStatus), noun-only (foldingRanges, contextBundle), prefix families (ctx*, butler*, batch*), and synonyms (get/fetch/list/search). It is readable, but not a predictable single convention across the whole server.
178 tools is an extreme overload for any single MCP server, far beyond the typical 3-15 range. The count alone makes discovery, selection, and maintenance impractical, even if many tools are individually useful.
The server covers a broad IDE/bridge/connector surface, but there are notable lifecycle gaps. For example, getPRTemplate references githubCreatePR, which is absent; git merge/rebase/tag/delete-branch are missing; and GitHub issue create/update/comment are absent despite Linear CRUD support.