Secure Local Workspace MCP
Related Servers
Alternatives to Secure Local Workspace MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to operate authorized local projects through MCP, including reading and modifying code, viewing Git changes, running configured programs, and reading local Codex sessions to continue work.02MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to securely access explicitly authorized local project files and run approved development commands with bounded execution and audit logging.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to inspect and edit local projects through a secure MCP interface, offering workspace management, file operations, git integration, and safe command execution.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT web to safely read and modify only explicitly allowed local project files through OpenAI Secure MCP Tunnel, including git operations, file edits, and running project scripts, while enforcing strict security boundaries.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT or any MCP client to operate safely on a designated workspace by listing, reading, searching, writing, and trashing files, inspecting Git status/log/diff, and optionally running allowlisted executables without a shell.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to read and edit local project files, inspect Git changes, and run approved development scripts through a secure MCP tunnel, with optional Codex Desktop integration.177 npm2Apache 2.0
TDQS
Scored across 17 tools
Each tool targets a distinct operation—project discovery/auth, file read/write, git workflow, or task execution—so an agent can reliably select based on action. The only mild pairing is list_projects vs discover_projects, but their descriptions clearly separate authorized projects from available ones.
Most tools follow a predictable verb_noun pattern like list_files, read_file, apply_patch, and run_task. diagnostics is a noun-style outlier, and the git_* family uses command nouns (git_status, git_diff) rather than verbs, but the overall pattern remains recognizable.
At 17 tools, the server is slightly above the typical 3–15 range, but the count is justified by covering project discovery, authorization, file editing, git operations, and task execution. Each tool earns its place and none feel redundant.
The toolset covers project lifecycle, file CRUD/search, core git commit/push workflows, and configured task execution with no dead ends. Minor gaps like file rename/move or git branch/log operations are not essential to the secure workspace purpose but could be nice additions.