A
licenseNot graded
qualityA
maintenanceA desktop launcher and local MCP workspace server that enables ChatGPT and other MCP clients to securely read, edit, search, run commands, and show changes in selected local project folders.
1
MIT
ChampCity GPT MCP Launcher
Related Servers
Alternatives to ChampCity GPT MCP Launcher
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn unofficial self-hosted MCP server that enables ChatGPT to run commands on your computer through a secure tunnel, manage processes, and work within a specified project directory.1-
- AlicenseBqualityDmaintenanceSelf-hosted MCP server that enables ChatGPT to access and operate on local project files after OAuth authorization, without uploading the workspace elsewhere.38108MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that lets ChatGPT securely read, edit, search, and run code in your local projects via an owner-approved connection.1,205 npmMIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server enabling Codex and ChatGPT to read/write files, execute commands, manage processes, use Git, and inspect images on the user's machine with full privileges.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server that lets ChatGPT work with your local codebase through explicit tools.MIT
TDQS
B3.4/5.0
Scored across 19 tools
Disambiguation5/5
Each tool targets a distinct domain or action: Figma-related tools are clearly separate from git, file, and workspace/release status tools. Even within similar categories (e.g., multiple get_*_summary tools), each refers to a different entity (builder report, release artifact, etc.), so there is no ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case, such as fetch_, get_, git_, list_, parse_, propose_, read_, search_, test_, and pre_commit_safety_scan. The style is uniform, making it easy for an agent to predict tool names.
Tool Count4/5
With 19 tools, the server covers multiple areas (Figma, git, files, workspace, releases, scanning) without feeling bloated. While slightly above the ideal range, each tool appears justified for the launcher's intended scope.
Completeness3/5
The tool surface is notably read-only; there are no tools for writing files, committing, pushing, or applying patches (despite propose_patch referencing an apply_approved_patch, which is absent). This leaves significant gaps for full workflows, though it may be intentional for a review-only launcher.
Maintenance
ActivityStale
ResponsivenessNo issues