OppenSteward-MCP
Related Servers
Alternatives to OppenSteward-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to read local project facts and manage Codex Desktop tasks through the official Secure MCP Tunnel.11MIT
- 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.493 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT to save conversation attachments, generated files, and images directly into a configured local macOS project directory with OAuth-secured MCP access.MIT
- 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.112 npm4Apache 2.0
- 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 gradedqualityAmaintenanceEnables ChatGPT to securely access project files and directories, read and write text files, and run allowlisted PowerShell commands on a Windows machine through an OpenAI Secure MCP Tunnel.MIT
TDQS
Scored across 8 tools
The three listing/introspection tools (list_files, list_projects, project_overview) overlap substantially—all touch the project registry and indexed paths—and fetch vs read_file both retrieve document content by different keying schemes. Detailed descriptions and cross-references help, but an agent could still misselect among the registry-related tools.
Names are consistently snake_case with a mostly verb_noun pattern (list_files, list_projects, refresh_projects, get_skill_guide, read_file). Minor deviations: 'search' and 'fetch' are bare verbs, and 'project_overview' is noun-style, but the set remains predictable.
Eight tools is well-scoped for a read-only governance/registry browsing server. Each tool maps to a distinct capability (enumerate projects, browse paths, search, retrieve, read chunks, load skill docs) without obvious padding.
The surface is read-only and coherent, but the descriptions repeatedly reference list_discussions and read_discussion—tools that are not included in this set—creating dead-end pointers and a notable gap in the Discussion workflow it claims to support. Core search/fetch/read lifecycle is otherwise covered.