Skip to main content
Glama
tksfjt1024

codex-cli-mcp-slim

by tksfjt1024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEX_CMDNoPath to the codex CLI binarycodex
CODEX_CLI_MCP_SLIM_TIMEOUTNoDefault subprocess timeout in seconds1800
CODEX_CLI_MCP_SLIM_LOG_LEVELNoLogging level for stderr diagnosticsINFO

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
codexB

Run a single non-interactive Codex session (codex exec) with the given prompt and return its final message. codex is an agentic coding assistant that reads and, depending on the sandbox, edits files inside the working directory. Forward-compatible: unknown CLI flags can be passed via extra_args. The codex binary path is configurable via $CODEX_CMD.

codex-replyA

Continue a previous Codex session (codex exec resume <THREAD_ID>) with a follow-up prompt and return the new final message. Only the flags codex exec resume accepts are exposed; the working directory and sandbox come from the current configuration (this server's own flags and config.toml), not from the original session.

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

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: `codex` starts a non-interactive Codex session, while `codex-reply` resumes an existing session by THREAD_ID. Agents can easily choose between initial execution and continuation without overlap.

Naming Consistency4/5

Both names share the `codex` prefix and use kebab-case, making the relationship obvious. However, the first tool is a bare noun while the second appends an action-like suffix, so it is not a uniform verb_noun convention.

Tool Count4/5

Two tools is slightly under the typical 3-15 range, but for a deliberately slim CLI wrapper it is well-scoped. Each tool earns its place: one starts a session, one continues it.

Completeness4/5

The set covers the core Codex session lifecycle: start a session and continue it with a follow-up prompt. It lacks broader session management such as listing, cancelling, or checking status, but these are minor gaps given the slim wrapper scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources