Skip to main content
Glama
ossmalaysia

codex-local-mcp

by ossmalaysia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-local-mcp

No user-submitted related servers found.

    Related Servers

    • TaskQuay

      lxjmaster
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT conversations to directly inspect local workspaces and delegate coding tasks to a local Codex agent, with controlled concurrency, reusable sessions, and task/usage tracking.
      587 npm
      MIT

    • codex-mcp

      alvarosw
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.
      9
      3 npm
      MIT

    • Codex MCP Server

      cexll
      A
      license
      C
      quality
      F
      maintenance
      Connects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.
      8
      93 npm
      178
      MIT

    • local-code-agent

      jhonsmithsamsmith
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables external AI (ChatGPT, Claude) to securely access a local workspace via Cloudflare Tunnel, providing file operations, shell commands, Git operations, and more with bearer token authentication and sandbox isolation.
      1
      -

    • Codex MCP Server

      SpongeBaby-124
      F
      license
      B
      quality
      D
      maintenance
      Connects AI assistants to a local Codex engine for performing deep, project-level code reviews and automated refactoring. It enables context-aware bug fixes and multi-file analysis through a standardized bridge between modern AI clients and local development environments.
      4
      2
      -
    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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: running a coding task, generating images, polling async job results, and reading workspace artifacts. There is no overlap or ambiguity between them.

    Naming Consistency3/5

    All tools share the codex_ prefix, but the pattern is inconsistent: codex_run and codex_generate_image are verb-led, codex_read_artifact is verb_noun, while codex_job_result is noun_noun. The naming is readable but not uniform.

    Tool Count4/5

    Four tools is a compact but reasonable set for a local Codex CLI integration. Each tool serves a necessary function in the workflow, though the surface is slightly minimal.

    Completeness4/5

    The core lifecycle of submitting a task, polling for results, and reading generated artifacts is covered. Minor gaps exist, such as no way to cancel a running job or list available workspace files, but these are not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources