plunger
OfficialRelated Servers
Alternatives to plunger
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted server that lets ChatGPT, Grok, and stdio MCP clients read and write files, run PowerShell/CMD and interactive processes, and drive the Windows desktop through screenshots, window info, clicks, drags, and keyboard input. It connects via OpenAI Secure MCP Tunnels, an OAuth authorization-code + S256 PKCE HTTPS endpoint, or local stdio, exposing 38 tools under the user's own Windows account.MIT
- FlicenseNot gradedqualityFmaintenanceA lightweight MCP HTTP server giving AI assistants real tools to interact with your Windows machine, including running commands, file access, system info, web search, and browser automation.1-
- AlicenseNot gradedqualityCmaintenanceA tiny local MCP server and CLI that lets AI agents read only allowlisted environment variables, redacts known secrets from text, and logs every access.MIT
- FlicenseAqualityDmaintenanceUniversal HTTP client tool for LLM agents. Enables Claude and other MCP-compatible agents to perform GET, POST, PUT, DELETE, and other HTTP requests to any URL, including localhost and internal network addresses.2-
- AlicenseNot gradedqualityBmaintenanceRemote-first, model-independent Windows execution MCP for ChatGPT, Claude, Gemini, and other MCP-compatible AI clients.MIT
- AlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 tools over a single OAuth-gated MCP endpoint, letting web-based AI chat clients read and edit local files, run whitelisted shell commands, search, use Git, inspect SQLite databases, and drive browser, DevTools, clipboard, and background-task workflows. It requires no system-wide install or admin rights and restricts access to folders and commands approved from a local control panel.MIT
TDQS
Scored across 17 tools
Each tool has a clearly distinct resource and action: requests vs workflows vs variables vs history vs curl conversion vs grouping. Overlaps like get_history/get_history_entry and save_request/save_workflow are conventional list-vs-detail or resource-type distinctions that the descriptions make clear.
All tool names follow a consistent snake_case verb_noun pattern such as list_saved_requests, save_workflow, delete_variable, and get_history_entry. There are no mixed conventions or vague standalone verbs.
With 17 tools, the set is slightly above the typical well-scoped range but still reasonable for an HTTP client/workflow manager with requests, workflows, variables, history, curl conversion, and grouping. Each tool earns its place, though the surface is somewhat broad.
The server covers request sending, saved request lifecycle, workflow save/list/run/delete, variables list/set/delete, history viewing, curl import/export, and grouping. Minor gaps exist, such as no explicit workflow update operation and no history deletion, but core workflows are well covered.