claude-codex-settings

This MCP server provides the Claude Codex Settings integration for managing Claude Code plugins and related configuration within the MCP ecosystem. It leverages the Claude Codex workflow to coordinate settings, synchronization of CLAUDE.md content, and allowlists across the CLAUDE Codex setup. With this MCP server active, you can leverage the associated MCP endpoints to organize and apply configuration changes to your Claude Code environment, and coordinate between CLAUDE.md instructions, the permissions allowlist, and context-refresh workflows. The repository’s documentation indicates a broad plugin system (Azure MCP, GCloud MCP, MongoDB MCP, Slack MCP, etc.) and this MCP server focuses on centralizing Codex-specific settings, synchronization tasks, and hooks that support consistent behavior across plugins and skills. Use the server to access or trigger settings synchronization, context refresh routines, and any Codex-specific configuration commands exposed by the MCP layer.

Prerequisites:

• Node.js installed on the host where you run the MCP server (recommended LTS version).
• Access to the Claude Code environment or a compatible MCP runner that supports the MCP protocol.
• Basic familiarity with running Node.js applications and starting an MCP server.

Installation steps:

1. Prepare the environment

   • Ensure Node.js is installed: node -v and npm -v should return version numbers.
   • Create a project directory for the MCP server or clone the repository that contains claude-codex-settings.

2. Install dependencies (if a package.json exists)

npm install

3. Run the MCP server

node server.js

4. Verify the server is up

• Check the console for a listening port (e.g., Listening on port 3000) or use curl to hit the MCP endpoint.
• If a specific port is required by your MCP environment, set PORT accordingly:

PORT=3000 node server.js

5. Integrate with your MCP orchestrator

• Register the server under the MCP framework using your platform’s configuration (e.g., add claude-codex-settings as a server in your MCP registry).
• If applicable, ensure any required environment variables (like CLAUDE_API_KEY) are provided in your deployment environment or via your orchestration tooling.

Tips and common considerations:

• The CLAUDE_API_KEY (or equivalent) may be required if the server calls out to Claude services for synchronization or content operations. Do not commit secrets; use your environment’s secret management.
• If you modify environment variables, restart the MCP server for changes to take effect.
• Review any relevant llms.txt or plugin documentation referenced in the repository README to understand how CLAUDE.md synchronization interacts with MCP flows.
• Ensure compatibility with your Claude Code plugins set, particularly those related to CLAUDE.md synchronization and allowlists.
• If you encounter port conflicts, adjust the PORT variable or configure the MCP orchestrator to route to a dedicated port for this server.