agentleFS
Sign inStart free
anyoneandersonanyoneanderson/agent-skills/skills/mcp-convert/SKILL.md

mcp-convert

Skill3 starsChanged 9 days agoMITView on GitHub

MCP config converter for agent CLIs.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer concise operational guidance over long explanation.

    line 36
  2. Very specific:

    Use AskUserQuestion for user decisions.

    line 40
  3. Very specific:

    After reading ~/.claude.json, show the discovered Claude MCP servers.

    line 45
  4. Distinctive:

    If more than one server exists, use AskUserQuestion to ask what to migrate.

    line 46
  5. Distinctive:

    only servers with secrets

    line 50
  6. Distinctive:

    If the user did not explicitly ask to mutate Codex config, ask whether to:

    line 54
  7. Distinctive:

    Ask whether to dry-run, apply, or export TOML.

    line 65
  8. Very specific:

    Run the converter with --mode dry-run

    line 83
  9. Distinctive:

    Ask which servers to migrate:

    line 85
  10. Distinctive:

    Use AskUserQuestion if multiple servers are available and the user did not already specify the selection

    line 86
  11. Distinctive:

    Use AskUserQuestion unless the user clearly asked to apply immediately

    line 91
  12. Very specific:

    If Claude has project-local MCP overrides, inspect them separately.

    line 129
  13. Distinctive:

    If a server type is unsupported, report it clearly and skip it rather than guessing.

    line 130
  14. Very specific:

    When presenting discovered servers, include whether each server has env keys.

    line 131

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

mcp-convert — Convert MCP Configuration

Convert Claude Code MCP settings into Codex CLI MCP configuration.

Language Rules

  1. Auto-detect the user's language and respond in the same language.
  2. Prefer concise operational guidance over long explanation.

Interaction Policy: AskUserQuestion

Use AskUserQuestion for user decisions. Do not jump straight to apply when the request is ambiguous or when multiple MCP servers are available.

Required decision points

  1. Server selection
    • After reading ~/.claude.json, show the discovered Claude MCP servers.
    • If more than one server exists, use AskUserQuestion to ask what to migrate.
    • Recommended first option: migrate all discovered servers.
    • Other options may be grouped, for example:
      • all servers
      • only servers with secrets
      • select a subset manually
  2. Apply mode
    • If the user did not explicitly ask to mutate Codex config, ask whether to:
      • dry-run only (Recommended)
      • apply immediately
      • export TOML only

Suggested AskUserQuestion flow

Round 1:

  • Show discovered MCP servers and ask what to migrate.

Round 2:

  • Ask whether to dry-run, apply, or export TOML.

Skip questions already answered by the user. If the user clearly says things like "move all of them", do not re-ask that decision.

What This Skill Does

This skill uses the bundled converter script:

scripts/convert_claude_to_codex.py

The script reads Claude Code MCP definitions from ~/.claude.json and converts them for Codex. Env values from Claude config are copied directly into Codex config.

Execution Flow

  1. Confirm the source file exists:
    • ~/.claude.json
  2. Preview the available Claude MCP servers:
    • Run the converter with --mode dry-run
    • Summarize discovered server names for the user
  3. Ask which servers to migrate:
    • Use AskUserQuestion if multiple servers are available and the user did not already specify the selection
  4. Ask execution mode:
    • dry-run
    • apply
    • export-toml
    • Use AskUserQuestion unless the user clearly asked to apply immediately
  5. Execute the selected action
  6. Verify:
    • Run codex mcp list

Recommended Commands

Preview

python3 skills/mcp-convert/scripts/convert_claude_to_codex.py --mode dry-run

Apply

python3 skills/mcp-convert/scripts/convert_claude_to_codex.py --mode apply --overwrite

Export TOML only

python3 skills/mcp-convert/scripts/convert_claude_to_codex.py --mode export-toml

Options

OptionUse when
--mode dry-runShow what will be converted without changing Codex
--mode applyRegister MCP servers into Codex
--mode export-tomlProduce TOML for inspection or manual use
--overwriteReplace existing Codex MCP entries of the same name
--server <name>Convert only selected servers

Notes

  • Env values from Claude config are copied directly into Codex config as plaintext.
  • If Claude has project-local MCP overrides, inspect them separately; the converter targets the top-level mcpServers block in ~/.claude.json.
  • If a server type is unsupported, report it clearly and skip it rather than guessing.
  • When presenting discovered servers, include whether each server has env keys.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free