freemcplab / Directory / Playground / Claude + Codex Settings

● Community fcakyon ⚡ Instant

Claude + Codex Settings

Name: Claude + Codex Settings (Claude Skill)
Author: fcakyon

by fcakyon · fcakyon/claude-codex-settings

An opinionated, working configuration for Claude Code AND OpenAI Codex — skills, plugins, hooks, MCPs, all known-good.

Useful as a reference point: instead of starting from blank settings.json, fork this repo and trim. Covers commonly-needed hooks (formatting, lint), permission allowlists, MCP configs that play together, and skills the author actually uses.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Known-good settings.json for both Claude Code and Codex
Pre-tuned permission allowlists
Hooks for formatter / linter / typechecker
Curated set of MCPs that compose well
Personal but documented choices

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-codex-settings-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/fcakyon/claude-codex-settings"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-codex-settings-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/fcakyon/claude-codex-settings"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-codex-settings-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/fcakyon/claude-codex-settings"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-codex-settings-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/fcakyon/claude-codex-settings"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-codex-settings-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/fcakyon/claude-codex-settings"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-codex-settings-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/fcakyon/claude-codex-settings"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-codex-settings-skill -- git clone https://github.com/fcakyon/claude-codex-settings

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Claude + Codex Settings

Bootstrap a working Claude Code config from a known-good baseline

👤 Claude Code users ⏱ ~15 min intermediate

When to use: You're tired of starting from a blank slate.

Flow

Clone

Clone into a scratch folder.✓ Copied

→ Files visible
Pick + trim

Copy what you need into your real ~/.claude; remove what you don't✓ Copied

→ Personalized config
Iterate

Tweak permissions and hooks based on real usage✓ Copied

→ Stable setup

Outcome: Config that already covers the obvious things, customized to your style.

Combinations

Pair with other MCPs for X10 leverage

claude-codex-settings-skill + fewer-permission-prompts (built-in skill)

Use it to slim the allowlist further to your usage

Combine claude-codex-settings-skill with fewer-permission-prompts (built-in skill): Use it to slim the allowlist further to your usage✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
reference-config	(see docs)	Static config files; not callable tools	1 call

Cost & Limits

What this costs to run

API quota: N/A
Tokens per call: 0
Monetary: Free
Tip: Don't copy blindly — author's preferences may not match yours

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: None by itself

Never grant: blindly trust permission entries; review them

Troubleshooting

Common errors and fixes

Some MCPs not starting

Author's versions may be outdated; bump npm package versions

Alternatives