data-ai MCP Server
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Discovered via github-topic:mcp and last synced Today.
1. Install the package
npx ecc-universal
2. Add to claude_desktop_config.json
{
"mcpServers": {
"ecc-universal": {
"command": "npx",
"args": [
"ecc-universal"
]
}
}
}Config file location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows)
REST API design patterns
Multi-platform content distribution across X, LinkedIn, Threads
Shared
Git worktrees, cascade method, when to scale instances
`.codex/agents/`: explorer, reviewer, docs-researcher
Beta built plugin
`refactor` prompt
Via instructions
Shared (AGENTS.md)
N/A
Shared
strict` and `ECC_DISABLED_HOOKS=...` for runtime gating without editing hook files. - **New harness commands**: `/harness-audit`, `/loop-start`, `/loop-status`, `/quality-gate`, `/model-route`. - **NanoClaw v2**: model routing, skill hot-load, session branch/search/export/compact/metrics. - **Cross-harness parity**: behavior tightened across Claude Code, Cursor, OpenCode, and Codex app/CLI. - **997 internal tests passing**: full suite green after hook/runtime refactor and compatibility updates. ### v1.7.0: Cross-Platform Expansion and Presentation Builder (Feb 2026) - **Codex app + CLI support**: Direct `AGENTS.md`-based Codex support, installer targeting, and Codex docs - **`frontend-slides` skill**: Zero-dependency HTML presentation builder with PPTX conversion guidance and strict viewport-fit rules - **5 new generic business/content skills**: `article-writing`, `content-engine`, `market-research`, `investor-materials`, `investor-outreach` - **Broader tool coverage**: Cursor, Codex, and OpenCode support tightened so the same repo ships cleanly across all major harnesses - **992 internal tests**: Expanded validation and regression coverage across plugin, hooks, skills, and packaging ### v1.6.0: Codex CLI, AgentShield, and Marketplace (Feb 2026) - **Codex CLI support**: New `/codex-setup` command generates `codex.md` for OpenAI Codex CLI compatibility - **7 new skills**: `search-first`, `swift-actor-persistence`, `swift-protocol-di-testing`, `regex-vs-llm-structured-text`, `content-hash-cache-pattern`, `cost-aware-llm-pipeline`, `skill-stocktake` - **AgentShield integration**: `/security-scan` runs AgentShield directly from Claude Code; 1282 tests, 102 rules - **GitHub Marketplace**: ECC Tools GitHub App live at [github.com/marketplace/ecc-tools](https://github.com/marketplace/ecc-tools) with free/pro/enterprise tiers - **30+ community PRs merged**: Contributions from 30 contributors across 6 languages - **978 internal tests**: Expanded validation suite across agents, skills, commands, hooks, and rules ### v1.4.1: Bug Fix (Feb 2026) - **Fixed instinct import content loss**: `parse_instinct_file()` was silently dropping all content after frontmatter (Action, Evidence, Examples sections) during `/instinct-import`. ([#148](https://github.com/affaan-m/ECC/issues/148), [#161](https://github.com/affaan-m/ECC/pull/161)) ### v1.4.0: Multi-Language Rules, Installation Wizard, and PM2 (Feb 2026) - **Interactive installation wizard**: New `configure-ecc` skill provides guided setup with merge/overwrite detection - **PM2 and multi-agent orchestration**: 6 new commands (`/pm2`, `/multi-plan`, `/multi-execute`, `/multi-backend`, `/multi-frontend`, `/multi-workflow`) for managing complex multi-service workflows - **Multi-language rules architecture**: Rules restructured from flat files into `common/` + `typescript/` + `python/` + `golang/` directories. Install only the languages you need - **Chinese (zh-CN) translations**: Complete translation of all agents, commands, skills, and rules (80+ files) - **GitHub Sponsors support**: Sponsor the project via GitHub Sponsors - **Enhanced CONTRIBUTING.md**: Detailed PR templates for each contribution type ### v1.3.0: OpenCode Plugin Support (Feb 2026) - **Full OpenCode integration**: 12 agents, 24 commands, 16 skills with hook support via OpenCode's plugin system (20+ event types) - **3 native custom tools**: run-tests, check-coverage, security-audit - **LLM documentation**: `llms.txt` for comprehensive OpenCode docs ### v1.2.0: Unified Commands and Skills (Feb 2026) - **Python/Django support**: Django patterns, security, TDD, and verification skills - **Java Spring Boot skills**: Patterns, security, TDD, and verification for Spring Boot - **Session management**: `/sessions` command for session history - **Continuous learning v2**: Instinct-based learning with confidence scoring, import/export, evolution See the full changelog in [Releases](https://github.com/affaan-m/ECC/releases). </details> ## Why Choose ECC?
### Common Workflows Slash forms below are shown where they remain part of the maintained command surface. Retired short-name shims such as `/tdd` and `/eval` live in `legacy-command-shims/` for explicit opt-in only. **Starting a new feature:** ``` /everything-claude-code:plan "Add user authentication with OAuth" → planner creates implementation blueprint tdd-workflow skill → tdd-guide enforces write-tests-first /code-review → code-reviewer checks your work ``` **Fixing a bug:** ``` tdd-workflow skill → tdd-guide: write a failing test that reproduces it → implement the fix, verify test passes /code-review → code-reviewer: catch regressions ``` **Preparing for production:** ``` /security-scan → security-reviewer: OWASP Top 10 audit e2e-testing skill → e2e-runner: critical user flow tests /test-coverage → verify 80%+ coverage ``` --- ## FAQ <details> <summary><b>How do I check which agents/commands are installed?</b></summary> ```bash /plugin list everything-claude-code@everything-claude-code ``` This shows all available agents, commands, and skills from the plugin. </details> <details> <summary><b>My hooks aren't working / I see "Duplicate hooks file" errors</b></summary> This is the most common issue. **Do NOT add a `"hooks"` field to `.claude-plugin/plugin.json`.** Claude Code v2.1+ automatically loads `hooks/hooks.json` from installed plugins. Explicitly declaring it causes duplicate detection errors. See [#29](https://github.com/affaan-m/everything-claude-code/issues/29), [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/everything-claude-code/issues/103). </details> <details> <summary><b>Can I use ECC with Claude Code on a custom API endpoint or model gateway?</b></summary> Yes. ECC does not hardcode Anthropic-hosted transport settings. It runs locally through Claude Code's normal CLI/plugin surface, so it works with: - Anthropic-hosted Claude Code - Official Claude Code gateway setups using `ANTHROPIC_BASE_URL` and `ANTHROPIC_AUTH_TOKEN` - Compatible custom endpoints that speak the Anthropic API Claude Code expects Minimal example: ```bash export ANTHROPIC_BASE_URL=https://your-gateway.example.com export ANTHROPIC_AUTH_TOKEN=your-token claude ``` If your gateway remaps model names, configure that in Claude Code rather than in ECC. ECC's hooks, skills, commands, and rules are model-provider agnostic once the `claude` CLI is already working. Official references: - [Claude Code LLM gateway docs](https://docs.anthropic.com/en/docs/claude-code/llm-gateway) - [Claude Code model configuration docs](https://docs.anthropic.com/en/docs/claude-code/model-config) </details> <details> <summary><b>My context window is shrinking / Claude is running out of context</b></summary> Too many MCP servers eat your context. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k. SessionStart context is capped at 8000 characters by default; lower it with `ECC_SESSION_START_MAX_CHARS=4000` or disable it with `ECC_SESSION_START_CONTEXT=off` for local-model or low-context setups. **Fix:** Disable unused MCPs from Claude Code with `/mcp`. Claude Code writes those runtime choices to `~/.claude.json`; `.claude/settings.json` and `.claude/settings.local.json` are not reliable toggles for already-loaded MCP servers. Keep under 10 MCPs enabled and under 80 tools active. </details> <details> <summary><b>Can I use only some components (e.g., just agents)?</b></summary> Yes. Use Option 2 (manual installation) and copy only what you need: ```bash # Just agents cp everything-claude-code/agents/*.md ~/.claude/agents/ # Just rules mkdir -p ~/.claude/rules/ecc/ cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/ ``` Each component is fully independent. </details> <details> <summary><b>Does this work with Cursor / OpenCode / Codex / Antigravity?</b></summary> Yes. ECC is cross-platform: - **Cursor**: Pre-translated configs in `.cursor/`. See [Cursor IDE Support](#cursor-ide-support). - **Gemini CLI**: Experimental project-local support via `.gemini/GEMINI.md` and shared installer plumbing. - **OpenCode**: Full plugin support in `.opencode/`. See [OpenCode Support](#opencode-support). - **Codex**: First-class support for both macOS app and CLI, with adapter drift guards and SessionStart fallback. See PR [#257](https://github.com/affaan-m/everything-claude-code/pull/257). - **Antigravity**: Tightly integrated setup for workflows, skills, and flattened rules in `.agent/`. See [Antigravity Guide](docs/ANTIGRAVITY-GUIDE.md). - **Non-native harnesses**: Manual fallback path for Grok and similar interfaces. See [Manual Adaptation Guide](docs/MANUAL-ADAPTATION-GUIDE.md). - **Claude Code**: Native — this is the primary target. </details> <details> <summary><b>How do I contribute a new skill or agent?</b></summary> See [CONTRIBUTING.md](CONTRIBUTING.md). The short version: 1. Fork the repo 2. Create your skill in `skills/your-skill-name/SKILL.md` (with YAML frontmatter) 3. Or create an agent in `agents/your-agent.md` 4. Submit a PR with a clear description of what it does and when to use it </details> --- ## Running Tests The plugin includes a comprehensive test suite: ```bash # Run all tests node tests/run-all.js # Run individual test files node tests/lib/utils.test.js node tests/lib/package-manager.test.js node tests/hooks/hooks.test.js ``` --- ## Contributing **Contributions are welcome and encouraged.** This repo is meant to be a community resource. If you have: - Useful agents or skills - Clever hooks - Better MCP configurations - Improved rules Please contribute! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. ### Ideas for Contributions - Language-specific skills (Rust, C#, Kotlin, Java) — Go, Python, Perl, Swift, and TypeScript already included - Framework-specific configs (Rails, FastAPI) — Django, NestJS, Spring Boot, and Laravel already included - DevOps agents (Kubernetes, Terraform, AWS, Docker) - Testing strategies (different frameworks, visual regression) - Domain-specific knowledge (ML, data engineering, mobile) ### Community Ecosystem Notes These are not bundled with ECC and are not audited by this repo, but they are worth knowing about if you are exploring the broader Claude Code skills ecosystem: - [claude-seo](https://github.com/AgriciDaniel/claude-seo) — SEO-focused skill and agent collection - [claude-ads](https://github.com/AgriciDaniel/claude-ads) — Ad-audit and paid-growth workflow collection - [claude-cybersecurity](https://github.com/AgriciDaniel/claude-cybersecurity) — Security-oriented skill and agent collection --- ## Cursor IDE Support ECC provides Cursor IDE support with hooks, rules, agents, skills, commands, and MCP configs adapted for Cursor's project layout. ### Quick Start (Cursor) ```bash # macOS/Linux ./install.sh --target cursor typescript ./install.sh --target cursor python golang swift php ``` ```powershell # Windows PowerShell .\install.ps1 --target cursor typescript .\install.ps1 --target cursor python golang swift php ``` ### What's Included
Thin Node.js scripts delegating to `scripts/hooks/` via shared adapter
`.cursor/mcp.json` if installed
Shared (AGENTS.md)
Anthropic Claude API patterns for Python and TypeScript
Playwright E2E tests
Purpose
`session.idle`
Personalized outreach, follow-ups, and intro blurbs
AI-assisted video editing workflows with FFmpeg and Remotion
`session.deleted`
Shared
95
Instruction-based
What You'll Learn
sessionStart, beforeShellExecution, afterFileEdit, beforeMCPExecution, beforeSubmitPrompt, and 10 more
2
Universal coding standards
Neural search via Exa MCP for web, code, company research
Comprehensive security checklist
Shared
Correctness, security, and missing-test review
Description
React/Next.js patterns
Shared
Development conventions and patterns for the project
Multi-agent orchestration using tmux pane manager
Shared
Source-derived writing style profiles from real content
Eval-driven development
48
5 prompts
Default
js
Shared
Source-attributed market and competitor research
Decks, memos, models, and one-pagers
Build, test, lint, typecheck, security
Documentation and API verification before release/docs changes
Claude Code
Shared (mcp.json)
GitHub, Context7, Exa, Memory, Playwright, Sequential Thinking (7 with Supabase via `--update-mcp` sync)
API design, database, caching
Test-driven development with 80%+ coverage
Shared (AGENTS.md)
N/A
Unified media generation for images, video, and audio
Shared
34
Long-form writing from notes and voice references
HTML presentations, PPTX conversion, visual style exploration
Context management
</details> <details> <summary><strong>Common workflows</strong></summary> Slash forms below are shown where they remain part of the maintained command surface. Retired short-name shims such as `/tdd` and `/eval` live in `legacy-command-shims/` for explicit opt-in only. **Starting a new feature:** ``` /ecc:plan "Add user authentication with OAuth" -> planner creates implementation blueprint tdd-workflow skill -> tdd-guide enforces write-tests-first /code-review -> code-reviewer checks your work ``` **Fixing a bug:** ``` tdd-workflow skill -> tdd-guide: write a failing test that reproduces it -> implement the fix, verify test passes /code-review -> code-reviewer: catch regressions ``` **Preparing for production:** ``` /security-scan -> security-reviewer: OWASP Top 10 audit e2e-testing skill -> e2e-runner: critical user flow tests /test-coverage -> verify 80%+ coverage ``` </details> ## Self-Hosted Models and Custom Endpoints ECC works through each harness's normal configuration, so you can use an official provider, a compatible custom API endpoint or model gateway, or a self-hosted model without changing ECC's workflows. For Claude Code, ECC does not hardcode Anthropic-hosted transport settings. Minimal gateway example: ```bash export ANTHROPIC_BASE_URL=https://your-gateway.example.com export ANTHROPIC_AUTH_TOKEN=your-token claude ``` If your gateway remaps model names, configure that in Claude Code rather than in ECC. ECC's hooks, skills, commands, and rules are model-provider agnostic once the `claude` CLI is already working. See Anthropic's [LLM gateway documentation](https://docs.anthropic.com/en/docs/claude-code/llm-gateway) and [model configuration documentation](https://docs.anthropic.com/en/docs/claude-code/model-config). Run or self-host any open-source model behind that gateway using separate compute and serving setup. If you need GPU capacity, [Itô](https://compute.itomarkets.com) is ECC's preferred compute sponsor; any GPU provider works. The sponsorship link is passive: it does not invoke an RFQ, reserve capacity, provision compute, or configure serving. Separately, `ecc ito find` invokes the explicitly configured canonical Itô CLI and submits a live authenticated RFQ; it does not reserve capacity. Managed inference through Itô is not live yet. ### Self-host Kimi with ECC + Itô compute The Kimi Code harness and the model-serving layer are separate. ECC configures the agent harness; you bring an API endpoint ([get a Kimi API key](https://platform.kimi.ai?aff=ecc)) or self-host an open-weight Kimi model on your own GPU capacity. This adapter is verified against Kimi Code 0.31.x (`@moonshot-ai/kimi-code`): <table aria-label="Local Kimi model path" width="100%"> <tr> <td width="33%" align="center"> <a href="https://compute.itomarkets.com"> <picture><source media="(prefers-color-scheme: light)" srcset="assets/images/sponsors/ito-transparent-light.png" /><img src="assets/images/sponsors/ito-transparent.png" width="92" alt="Itô Markets" /></picture><br /> <strong>1. Get GPU capacity</strong> </a><br /> <sub>Use Itô or any GPU provider.</sub> </td> <td width="33%" align="center"> <a href="https://www.moonshot.ai"> <picture><source media="(prefers-color-scheme: dark)" srcset="assets/images/sponsors/moonshot-dark.png" /><img src="assets/images/sponsors/moonshot.png" width="126" alt="Moonshot AI - Kimi" /></picture><br /> <strong>2. Serve Kimi</strong> </a><br /> <sub>Expose the chosen checkpoint through a compatible endpoint.</sub> </td> <td width="33%" align="center"> <a href=".kimi/README.md"> <img src="assets/images/community/ecc-tools-mark.svg" height="52" alt="ECC Tools" /><br /> <strong>3. Run Kimi Code with ECC</strong> </a><br /> <sub>Install project instructions and skills, then start Kimi Code.</sub> </td> </tr> </table> Configure the endpoint with Kimi Code's <a href="https://moonshotai.github.io/kimi-cli/en/configuration/providers.html">official provider guide</a>, then install ECC: ```bash bash ./install.sh --target kimi --profile minimal node scripts/ecc.js doctor --target kimi kimi ``` Kimi Code discovers the installed `.kimi-code/AGENTS.md` instructions and `.kimi-code/skills/` workflows natively; project-level `.agents/skills/` is also an official discovery location. ECC safely merges project MCP entries into `.kimi-code/mcp.json` and does not change the user-level `~/.kimi-code/config.toml`. Kimi Code supports native hooks, but ECC's current managed-project adapter does not configure them, so this installer does not offer Kimi hook profiles. The installer dry-run and regression suite verify that every managed Kimi write stays inside the project-local `.kimi-code/` root. ### Itô compute CLI bridge `ecc ito` delegates to the separately installed canonical Itô client; ECC does not maintain a second API client. `ecc ito login [--no-browser]` performs device authorization, opens the Itô verification page by default, and persists a device token in macOS Keychain; `--no-browser` suppresses the page handoff. ECC itself does no browser automation. `ecc ito auth` is validation-only and rejects `--no-browser`. The available operations are `ecc ito login`, `ecc ito auth`, `ecc ito find`, `ecc ito status`, and the separately gated `ecc ito evals`. The matching MCP tools remain `ito_auth`, `ito_find`, and `ito_status`; `ito_auth` validates existing credentials and node qualification is CLI-only. The `ito-compute-cli` package is currently unpublished. Build it locally from the Itô runtime repo (private while the desk hardens; design partners get access) under `cli/ito-compute-cli`, run `npm ci` and `npm run check`, then set `ECC_ITO_CLI_EXECUTABLE` to that build's absolute `dist/bin/ito.js` path. Login never inherits `ITO_API_KEY`; auth, find, and status forward `ITO_API_KEY` directly when configured, and `ITO_AUTH_MODE=legacy` is not required. `ecc ito logout` revokes the current device credential and retains its local copy if remote revocation cannot be confirmed. Device tokens use macOS Keychain by default; explicit file fallback must retain owner-only directory/file permissions. ECC does not discover this credential-bearing client through `PATH`. See the [`ito-compute` skill](skills/ito-compute/SKILL.md) for the full RFQ authority and MCP setup contract. `find` submits a live authenticated RFQ. It does not reserve capacity. `evals` requires both `ITO_ENABLE_SIXTYTWO_LIVE=1` and `--live-sixtytwo`, a separately installed `sixtytwo-cli==0.3.33`, an explicit node list, and an existing absolute configuration directory. It cannot rent, launch, recover, repair, or purchase. ECC exposes no quote lock, purchase, workload, or inference path, and it never replaces a missing client or failed live call with a local result. ## What's New Current release: **2.2.3** (2026-10-01). Highlights of the 2.2 line: - Guided, manifest-driven setup across Claude Code, Codex, and Kimi Code, with install-state ownership, doctor, repair, and uninstall. - Native Antigravity install, a thin Pi adapter, and the packed-artifact release gate tested on Linux, macOS, and Windows. - Plan Canvas browser review, the unified memory vault (`ecc memory`), and the Itô compute skill family. Full history: [CHANGELOG.md](CHANGELOG.md). Per-release notes and evidence live under [docs/releases/](docs/releases/). ### v2.0.0: The Agent Harness Operating System (Jun 2026) Stable graduation of the 2.0 line: control-pane substrate, worktree lifecycle service, the `orch-*` orchestrator family, and the Discord community. Notes: [docs/releases/2.0.0/release-notes.md](docs/releases/2.0.0/release-notes.md). ## What's Inside ```text ECC/
Plugin
Multi-source research with synthesis and source attribution
`tool.execute.before`
32
Details
Debug agent behavior, routing, and prompt boundaries
Next.js 16+ and Turbopack incremental bundling
Shared
Bun as runtime, package manager, bundler, and test runner
Sort agent catalogs and assignment surfaces
Shared
Shared
1
Shared
Shared
Root (universal) + `.codex/AGENTS.md` (Codex-specific supplement)
Description
Optional — Code Health MCP (opt-in server + token); structural review and commit/PR gates
Platform-native social content and repurposing
Up-to-date library and framework docs via Context7 MCP
Build MCP servers with Node/TypeScript SDK
Translate product goals into scoped capability maps
X/Twitter API integration for posting and analytics
Read-only codebase evidence gathering before edits
Scripts triggered by harness events
`tool.execute.after`
`session.created`
When to Use
File
Shared (AGENTS.md)
Shared
13 instructions
opus
31,999
on
Included
`./install.sh --profile minimal --target antigravity`
`./install.sh --profile minimal --target hermes`
`./install.sh --profile minimal --target openclaw`
What it does
Patterns learned from real sessions with confidence scores
Status
Supported core
Supported core
Checked-in instructions and prompt files
Claude Code
Native
Partial
Count
Enforcement, session summaries, continuous learning, instincts, and context controls
OpenCode
`./install.sh --profile minimal --target zed`
Supported native plugin
`./install.sh --profile minimal --target joycode`
`bunx [email protected] setup`
Status
`pnpm dlx [email protected] setup`
`./install.sh --profile minimal --target codebuddy`