Skip to main content
Glama
itto-ki

codex-cli-architect-mcp

by itto-ki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-cli-architect-mcp

No user-submitted related servers found.

    Related Servers

    • Agentic Developer MCP

      teabranch
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that wraps OpenAI's Codex CLI to automate repository cloning and code analysis tasks. It enables users to execute complex coding requests on specific Git branches and subfolders using standardized MCP tools.
      5 npm
      45
      MIT

    • codex-mcp-server

      etheaven
      A
      license
      B
      quality
      D
      maintenance
      An open-source MCP server that connects your IDE or AI assistant to the Codex CLI, enabling non-interactive automation with codex exec, safe sandboxed edits with approvals, and large-scale code analysis via @ file references.
      8
      15 npm
      MIT

    • Gemini Code Assist MCP

      VinnyVanGogh
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that integrates Google Gemini CLI with Claude Code for AI-powered development assistance, enabling code review, bug analysis, feature planning, and code explanation without requiring an API key.
      8
      MIT

    • Codex MCP Server

      tom-wahl
      F
      license
      B
      quality
      Not graded
      maintenance
      An MCP server for the OpenAI Codex CLI that provides coding assistance with multi-turn session management and reasoning depth control. It enables users to perform code analysis, generation, and refactoring through Claude with native resume support for conversational context.
      4
      577 npm
      1
      -
    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.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are largely distinct: consult is clearly separate, while explain and review both analyze code but differ in intent (understanding vs. critique). This boundary is clear enough for most cases, though explain and review could still be confused in edge scenarios.

    Naming Consistency5/5

    All tool names follow the same predictable pattern: codex_ prefix plus a lowercase imperative verb in snake_case. The naming is consistent and each verb clearly reflects the tool's purpose.

    Tool Count4/5

    Three tools is at the low end of the typical range, but each covers a distinct architect-focused activity: explain, consult, and review. The count is reasonable for a narrow assistant, though a broader architecture server could justify more tools.

    Completeness4/5

    The toolset covers core advisor-style workflows: understanding code, getting technical guidance, and reviewing changes. It lacks generative or planning tools, but that appears acceptable for an architect/consultant role rather than an active coding agent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources