Skip to main content
Glama
dpaula

chatgpt-codex-local-mcp

by dpaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to chatgpt-codex-local-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      1,521 npm
      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

    • Local Model Workers MCP

      gaabrielrd
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets Claude Code and Codex delegate repository exploration and test proposals to a remote LM Studio model, while enforcing security boundaries by keeping all repository access read-only and never applying patches or running commands remotely.
      9 npm
      1
      MIT

    • DevSpace

      chenchihcu
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that gives ChatGPT a secure connection to your local machine, enabling it to read, edit, search, and run code in your projects.
      1,521 npm
      MIT

    • otama

      Ronith2906
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI assistants safely access local git repositories, with free reads and gated writes requiring explicit confirmation.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action. The general exploration tools (list, read, search, git) are clearly separated, and each memory tool reads a specific, uniquely named file with no overlap.

    Naming Consistency5/5

    Tool names follow a consistent verb-first pattern: list_*, read_*, search_*, get_*. The memory tools all use read_<topic>_memory, with read_memory_index as a minor but still predictable deviation. Overall naming is highly uniform.

    Tool Count3/5

    At 17 tools, the server is slightly above the ideal 3-15 range. The 9 memory read tools are nearly identical operations on different files, inflating the count and adding unnecessary redundancy. A generic read_memory_file would reduce this.

    Completeness4/5

    For a read-only project exploration and memory reading server, the tool surface covers the core workflows: listing files, reading content, searching, and git status/diff. Minor gaps include no git log or branch listing, and memory files not in the predefined set require using read_file.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources