Skip to main content
Glama
autobelay

Codex Project-scoped MCP

by autobelay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Codex Project-scoped MCP

No user-submitted related servers found.

    Related Servers

    • codex-mcp-opencode

      Ichikawashadow
      A
      license
      A
      quality
      D
      maintenance
      A project-local MCP bridge that allows Codex Desktop to plan tasks and OpenCode to execute them within the current project directory, with session reuse and native OpenCode background subagents.
      4
      1
      MIT

    • Workspace Bridge MCP

      Yari-tuber
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables external MCP clients to discover and read a trusted VS Code workspace, inspect diagnostics and symbols, preview and apply conflict-safe edits, and run individually approved terminal commands through a local authenticated bridge.
      MIT

    • lsp-mcp

      kait-lgtm
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides any MCP-capable coding agent with shared, warm language-server intelligence and project-local configuration, so diagnostics, definitions, references, hover, symbols, code actions, formatting, rename, and sync behave consistently across harnesses and sessions. This lets users switch agent tools without reconfiguring LSP integrations or falling back to CLI verification.
      2 npm
      MIT

    • WebGPT Codex Bridge

      hsdc1258
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables continuing a local coding task from your own web ChatGPT account by exposing project-scoped read and apply tools over MCP, with no inference API dependency.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool in the set, there is no possibility of confusion or misselection. The tool has a single, clearly bounded purpose: reporting discovered project MCP config and connection status.

    Naming Consistency4/5

    The name project_mcp_status is clear, snake_case, and descriptive. However, it is a noun phrase without an action verb and a single sample cannot establish a predictable verb_noun pattern for the server.

    Tool Count3/5

    One tool is thin for a server whose name implies project-scoped MCP management. The diagnostic is plausible on its own, but the surface feels under-scoped relative to what the server's title suggests.

    Completeness2/5

    The surface is read-only status only: no per-server detail, no listing of individual tool names beyond counts, no reload/refresh of discovered config, and no way to act on the reported state. An agent that needs to inspect or fix MCP configuration will hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources