Skip to main content
Glama
workspace-json

@workspacejson/codex-mcp

Official

Related Servers

Alternatives to @workspacejson/codex-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding agents with pre-edit situational awareness by combining structural call graphs and co-change history to prevent incomplete edits. It surfaces files that historically change together, reducing missed coupled modules.
      3
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Temporal knowledge graph for codebases that captures decision traces, links test failures to code changes, learns co-edit patterns, predicts regression risk, and enforces learned constraints at the edit boundary via a PreToolUse hook.
      31
      22
      MIT
    • 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.
      1,342 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides a workspace-safe, read-only bridge between browser-based AI planning/review and local coding agents, enabling structured plan, execution summary, and review handoffs without granting shell, file write, or Git push access.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Analyzes code changes using static code-graph and git co-change history to identify likely affected files, returning tiered confidence reports with evidence. Exposes tools for AI assistants to inspect current changes, static impact, historical co-change patterns, and detailed explanations.
      5
      MIT

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: get context for a single file, list fragile files, and assess a set of file changes. There is no ambiguity or overlap.

    Naming Consistency5/5

    All tools follow a consistent 'workspace_verb_noun' pattern in snake_case, making them predictable and easy to understand.

    Tool Count5/5

    Three tools is well-scoped for a specialized server focused on workspace.json code intelligence; each tool earns its place without being too few or too many.

    Completeness5/5

    The tool surface covers the core operations for the domain: inspecting individual file history, listing high-risk files, and validating changes against historical data. No obvious gaps for its intended read-only analysis purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues