Reduce the default .mcp.json to one connector (chrome-devtools) per the new policy in docs/MCP-CONNECTOR-POLICY.md: a default earns its slot only if it is universal AND MCP beats a CLI/API wrapped in a skill. June 2026 audit verdicts: github -> gh via github-ops skill; context7 -> REST via documentation-lookup; exa -> harness-native search (+ exa-search skill); memory -> native harness memory + instincts; playwright -> playwright CLI skills (vendor moved agent flows off MCP); sequential-thinking -> native extended thinking. All six remain opt-in in mcp-configs/mcp-servers.json. Tests updated: plugin-manifest policy assertions + install-apply Cursor expectations. Co-authored-by: ECC Test <ecc@example.test>
2.8 KiB
.codex-plugin — Codex Native Plugin for ECC
This directory contains the Codex plugin manifest for ECC.
Structure
.codex-plugin/
└── plugin.json — Codex plugin manifest (name, version, skills ref, MCP ref)
.mcp.json — MCP server configurations at plugin root (NOT inside .codex-plugin/)
What This Provides
- 249 skills from
./skills/— reusable Codex workflows for TDD, security, code review, architecture, and more - 6 MCP servers — GitHub, Context7, Exa, Memory, Playwright, Sequential Thinking
Installation
Codex plugin support is marketplace-backed. The repo exposes a repo-scoped
marketplace at .agents/plugins/marketplace.json; Codex can add and track that
marketplace source from the CLI:
# Add the public repo marketplace
codex plugin marketplace add affaan-m/ECC
# Or add a local checkout while developing
codex plugin marketplace add /absolute/path/to/ECC
The marketplace entry points at the repository root so .codex-plugin/plugin.json,
skills/, and .mcp.json resolve from one shared source of truth. After adding
or updating the marketplace, restart Codex and install or enable ecc from the
plugin directory.
Official Plugin Directory publishing is coming soon. For official OpenAI
plugin-directory review, package this repo under the openai/plugins
repository shape: plugins/ecc/.codex-plugin/plugin.json,
plugins/ecc/skills/, and the supporting README/assets. Until that listing is
accepted, treat the public repo marketplace as the supported Codex distribution
path and keep release copy framed as repo-marketplace/manual installation.
The installed plugin registers under the short slug ecc so tool and command names
stay below provider length limits.
MCP Servers Included
| Server | Purpose |
|---|---|
chrome-devtools |
Interactive browser debugging via Chrome DevTools (CDP sessions, performance traces, console/network inspection) |
The former defaults (github, context7, exa, memory, playwright, sequential-thinking) were retired in the June 2026 connector audit — their jobs are covered by skills wrapping CLIs/REST APIs or by harness-native features. They remain available as opt-in entries in mcp-configs/mcp-servers.json. See docs/MCP-CONNECTOR-POLICY.md for the policy and the per-connector rationale.
Notes
- The
skills/directory at the repo root is the source of truth for the Codex plugin package; do not duplicate skill content inside.codex-plugin/. - ECC is moving to a skills-first workflow surface. Legacy
commands/remain for compatibility on harnesses that still expect slash-entry shims. - MCP server credentials are inherited from the launching environment (env vars)
- This manifest does not override
~/.codex/config.tomlsettings