Plugin
Related Servers
Alternatives to Plugin
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceA local MCP server that bridges ChatGPT to a Windows PC, offering filesystem, shell, Git, and diagnostic tools via a secure tunnel.171-
- AlicenseNot gradedqualityAmaintenanceThis local MCP runtime lets ChatGPT work with projects on your own device, run processes, and perform computer control. It also provides workspace browsing, Git repository and process management, plugin-attributed operation logs, and optional public access for remote MCP and WebUI use.473 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT on Windows to securely access codebases, Git, terminals, language servers, debuggers, SQLite, local HTTP services, adaptive project memory, engineering skills, checkpoints, audit logs, and sandboxed command execution through MCP tools.MIT
- FlicenseBqualityCmaintenanceChatGPT-compatible MCP server and Electron launcher for controlled local project-file access, providing read-only and approval-gated write tools over STDIO or HTTP with optional OAuth and HTTPS tunneling.19-
- AlicenseNot gradedqualityBmaintenanceA secure MCP server that gives ChatGPT access to local terminal, files, and background processes, and lets it discover, manage, and call any registered MCP server on the machine.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to safely interact with Windows workspaces through a loopback-only MCP server, with OAuth, bounded PowerShell tools, persistent jobs, and optional Cloudflare Tunnel exposure.MIT
TDQS
Scored across 2 tools
plugin_status and plugin_echo have distinct roles—one returns runtime identity, the other is an example echo—so they are not easily confused. However, plugin_echo's purpose is intentionally under-specified as a placeholder, leaving slight ambiguity about its intended use.
Both tools follow the same plugin_ prefix with snake_case noun suffixes (status, echo), giving a fully predictable naming pattern. There is no mixing of conventions or verb styles.
Two tools is thin for any server, and one is explicitly a placeholder to be replaced, so the set feels under-scoped. This is borderline rather than extreme, since a plugin scaffold might legitimately start small.
The surface has no real domain operations—just runtime identity and a placeholder echo—so it cannot support actual plugin workflows. Significant gaps remain before this could serve as a functional MCP server.