メニュー
Create or revise native Codex MCP definitions for stdio or HTTP servers with complete transport metadata, clear authentication, and pinned launchers. Use when exposing tools through a plugin or config.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Start here for the nddev-builder toolkit. Indexes the Codex artifact families and the creator, checker, reviewer, and workflow skill that owns each, points at the single reference for schemas and current (Beta, experimental, or under-development) surfaces, and routes the task to the right skill. Use first whenever building, checking, reviewing, or releasing a Codex artifact, or when unsure which builder skill applies.
A guided first run of the nddev-builder toolkit — from zero to a working, checked Codex artifact in ordered steps. Use when new to nddev-builder, onboarding, or unsure which builder skill to start with.
Create or revise a Codex marketplace catalog with valid plugin sources, categories, installation policy, and authentication policy. Use when publishing local or remote plugin collections.
Check a managed Codex requirements.toml layer for supported keys, permission-profile consistency, and a valid lower-layer default. Use before delivering managed /etc/codex or MDM requirements.
Create a managed Codex requirements.toml layer that constrains permission profiles and other admin policy. Use when authoring the /etc/codex or MDM-delivered managed requirements a lower config layer must satisfy.
Install and iterate on a Codex plugin locally in developer mode: the install, reinstall, and cachebuster test loop for a plugin under development, run against an isolated install and never live state. Use when running or iterating on a plugin, its skills, MCP, hooks, or bundled app locally.
| name | codex-mcp-creator |
| description | Create or revise native Codex MCP definitions for stdio or HTTP servers with complete transport metadata, clear authentication, and pinned launchers. Use when exposing tools through a plugin or config. |
Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.
Define an MCP server at the correct ownership surface with reproducible startup and no embedded credentials.
Choose the source surface first: plugin .mcp.json for bundled servers or config TOML for runtime-owned servers.
Read ../../references/codex-artifact-contracts.md for the current schema of that surface.
Inspect options and generate a plugin MCP definition when appropriate:
python3 ../../scripts/create_codex_artifact.py mcp --help
python3 ../../scripts/create_codex_artifact.py mcp --output . --name example-mcp --description "Expose a focused MCP tool surface" --command node --arg ./mcp/server.mjs
Preserve complete transport metadata. For stdio, specify command, argv, cwd, and environment references; for HTTP, specify URL and supported authentication metadata.
Pin package or binary versions when a launcher resolves mutable dependencies.
Keep tokens and credentials in approved environment or OAuth flows, never in source.
Validate:
python3 ../../scripts/check_codex_artifact.py mcp .mcp.json
Start or connect in an isolated environment, list tools, and exercise one read-only tool when possible.