An empty `tools/list` and a `not_implemented` envelope on `tools/call` is an unusual thing to document rather than paper over — execution is deferred and the local surface is read-only by design, so you know exactly what you are connecting. There is no public endpoint either: the Worker source ships, but you deploy it yourself. Start with the single read-only subagent before installing the suite; it needs nothing else.
A configuration layer for AI coding agents: a deep library of skills, commands, rules and personas, plus a capability router that loads the right skill on intent instead of dumping the whole catalog into context. It compiles into 20 host agents — Claude Code, Cursor, Augment, Cline, Windsurf, Copilot, Gemini CLI, Codex, Continue, Zed, JetBrains, Aider and more — and the MCP server is the read-only way to reach that content from any client.
- A read-only content surface over MCP — skills and commands served as prompts, rules and guidelines as resources; `tools/list` is empty and `tools/call` returns a `not_implemented` envelope by design
- Two entry points: a local stdio server (`agent-config mcp-server`) that needs no account and no network, and a self-hosted Cloudflare Worker for a shared team endpoint
- A 30-second starting point — a single read-only `production-validator` subagent dropped into any repository, which gates "done" by hunting mocks and stubs on the shipped path and demanding real-system evidence
- Governance compiled into each host's native rule format at projection time, with deterministic runtime hooks added on hook-capable hosts
- A detection-driven installer that finds your installed AI tools and pre-selects them, writing nothing until you click Finish
- Six role-shaped entry paths — developer, founder, content, agency, finance, ops — so you get a focused command set rather than the whole library
No account and no network for the local path: `npm install -g @event4u/agent-config` provides the `agent-config` binary, and the client entry is that command with the argument `mcp-server` — or `npx -y @event4u/agent-config mcp-server` if you would rather not install globally. Setup runs through `npx -y @event4u/agent-config init`, which launches a browser wizard on a terminal with a display and falls back to the non-interactive installer on CI, a non-TTY, a headless host, or when any CLI-mode flag is present; `--profile` and `--tools` pick your profile and hosts, and `--dry-run` previews writes. The remote path needs your own deployed Cloudflare Worker — the project ships the source but operates no shared hosted endpoint. Stdio-only clients reaching the Worker need the `mcp-remote` bridge.
One command — npx -y @event4u/agent-config mcp-server