Agentic Developer MCP Server

MCP server that wraps OpenAI Codex CLI and exposes MCP API

Local serverstdioPython

What is the Agentic Developer MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Agentic Developer MCP MCP server moves it into the conversation instead. MCP server that wraps OpenAI Codex CLI and exposes MCP API.

The short version

This project wraps OpenAI's Codex CLI as an MCP (Model Context Protocol) server, making it accessible through the TeaBranch/open-responses-server middleware. This engine may be replaced with OpenCode or Amazon Strands

  1. Codex CLI: OpenAI's command-line interface for interacting with Codex. 2. MCP Wrapper Server: A Node.js Express server that forwards MCP requests to Codex CLI and formats responses as MCP. 3. open-responses-server: A middleware service that provides Responses API compatibility and MCP support.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • run_codex — Clones a repository, checks out a specific branch (optional), navigates to a specific folder (optional), and runs Codex with the given request
  • Parameters — The Parameters tool exposed by this server
  • Example — The Example tool exposed by this server
  • clone_and_write_prompt — Clones a repository, reads the system prompt from .agent/system.md, parses modelId from .agent/agent.json, writes the request to a .prompt file, and

Getting it running

Installation goes through your MCP client rather than a global install: point it at @openai/codex on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

  • Node 22 (nvm install 22.15.1 | nvm use 22.15.1) required for Codex

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agentic Developer MCP's toolset — run_codex, Parameters, Example and 1 more — is a fair guide to whether it matches your workflow. It is maintained by teabranch; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agentic Developer MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
run_codexClones a repository, checks out a specific branch (optional), navigates to a specific folder (optional), and runs Codex with the given request.
ParametersThe Parameters tool exposed by this server.
ExampleThe Example tool exposed by this server.
clone_and_write_promptClones a repository, reads the system prompt from .agent/system.md, parses modelId from .agent/agent.json, writes the request to a .prompt file, and invokes the Codex CLI with the extracted model.

How to install the Agentic Developer MCP MCP server

{
  "mcpServers": {
    "agentic-developer": {
      "command": "npx",
      "args": ["-y", "@openai/codex"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node 22 (nvm install 22.15.1 | nvm use 22.15.1) required for Codex

Example prompts to try

  • Use Agentic Developer MCP to run codex.
  • Use Agentic Developer MCP to Parameters.
  • Use Agentic Developer MCP to Example.

Frequently asked questions

It connects Agentic Developer MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (run_codex, Parameters, Example, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agentic Developer MCP directly.