Skip to main content
Glama
dazebug

easy-codex-mcp

by dazebug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_new_conversationA

Start a new conversation with OpenAI Codex CLI.

Runs codex CLI in read-only sandbox mode and returns a thread_id for continuing the conversation later.

Limitations:

  • Runs in read-only sandbox — cannot modify files or execute shell commands.

  • Use only for read-only tasks: code reading, analysis, and Q&A.

When to use:

  1. Analyzing the structure or behavior of a codebase

  2. Code review or root cause analysis of bugs

  3. Generating explanations or documentation drafts for code

  4. Getting refactoring or architecture suggestions

Args: prompt: Prompt to send to codex. Use @filepath to mention files. working_directory: Directory path for codex to work in (optional).

Returns: Dict with thread_id and response.

continue_conversationA

Continue an existing Codex conversation.

Resumes a previous conversation using thread_id to maintain context. Same read-only sandbox limitations as start_new_conversation apply.

When to use:

  1. Asking follow-up questions based on previous analysis

  2. Continuing multi-step analysis on the same codebase

  3. Sending additional requests while maintaining conversation context

Args: thread_id: thread_id from a previous conversation. prompt: Follow-up prompt to send to codex. Use @filepath to mention files. working_directory: Directory path for codex to work in (optional).

Returns: Dict with thread_id and response.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one starts a new conversation and returns a thread_id, the other continues an existing conversation using that thread_id. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tool names follow the same verb_noun pattern with snake_case, using 'start_new_' and 'continue_' as clear action prefixes. This consistency makes the API predictable and easy to navigate.

Tool Count4/5

At only two tools, the count is on the low end but perfectly appropriate for the server's narrow purpose of managing Codex conversations. The tools cover the essential start/continue workflow without unnecessary additions.

Completeness4/5

The tool surface covers the primary conversation lifecycle (start and continue) with no dead ends. Minor gaps such as the absence of explicit conversation termination or history listing are acceptable given the read-only, session-based scope.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources