Skip to main content
Glama
ChampCityChris

ChampCity GPT MCP Launcher

by ChampCityChris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ChampCity GPT MCP Launcher

No user-submitted related servers found.

    Related Servers

    • BridgeDesk

      stanic-mah
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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

    • DevSpace

      CYZice
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that lets ChatGPT securely read, edit, search, and run code in your local projects via an owner-approved connection.
      583 npm
      MIT

    • local-terminal-mcp

      luckysolanki902
      A
      license
      A
      quality
      B
      maintenance
      Lets ChatGPT, Claude Desktop, Claude Code, and other MCP clients run an allowlisted set of local commands and read files from a chosen directory, so an assistant can analyse a codebase or trigger local generators (images, sprites, assets) without metered API tokens. The server is read-only and deny-by-default by default, with no shell, path containment, opt-in writes, and required auth when exposed over HTTP.
      3
      1
      MIT

    • Shared Credit Tool

      Minglink
      A
      license
      Not graded
      quality
      C
      maintenance
      Local 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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources