patterns + typical endpoint schemas — so v1 is just the swap to the real MCPserver + vault.
- **Voice**: warm welcome, no clinical process talk, no time estimates or unverified durations; compact/dense
printed command, surfaced in the UI and by `ccam update-check`.)
- `mcp/`: local MCPserver exposing dashboard operations as tools.
## Non-negotiable engineering rules
- Preserve existing behavior unless explicitly asked
write | Means |
|---|---|---|
| harness | host | Claude Code driving the session; "host" is the MCP host that spawns the server |
| foreign model | external model | any model not native to the harness
uninstall to test removal flow
/claude-delegator:uninstall
```
No build step, no dependencies. Uses native MCPservers from Codex and Gemini CLIs.
## Architecture
### Orchestration Flow
Claude acts as orchestrator—delegates
kubectl-mcp-server Project Memory
## Project Overview
- **Name**: kubectl-mcp-server
- **Version**: 1.22.0
- **Description**: A Model Context Protocol (MCP) server for Kubernetes with 270+ tools, 8 resources, and 8 prompts
environments`, `setup`)
- `references/` — shared docs referenced by skills via `../../references/…`
- `.mcp.json` — launches the FlowAgent MCPserver (registered as `flowagent`)
## Engine vs plugin
This folder is the **plugin**: skills, references, MCP
commands for shell access, scripts, and AI coding agents.
`mcpc` can connect to any MCPserver over Streamable HTTP or stdio transports,
securely login via OAuth credentials and store credentials
repository.
## Project Overview
mcp-framework is a TypeScript framework for building Model Context Protocol (MCP) servers. It provides an opinionated architecture with automatic directory-based discovery for tools, resources
Project Instructions for Claude
## Project Overview
**OpenTabs Platform** is a Chrome extension + MCPserver with a plugin-based architecture. A plugin SDK allows anyone to create OpenTabs plugins as standalone
Test Instructions
## Overview
Playwright E2E tests that exercise the full stack: MCPserver + Chrome extension + test web server + test plugin. Tests run under Playwright's Node.js test runner, so Node.js
dist/tools.json`, auto-registers the plugin in `localPlugins`, and calls `POST /reload` to notify the MCPserver)
## Plugin Icons
Place an `icon.svg` file in the plugin root directory. The build tool
During E2E, each Playwright worker (2 per container, via `CI=1`) spawns an MCPserver, a test server, and a Chromium instance (~600 MB each), totaling ~1.5 GB for Playwright
commands, conventions, release flow, and gotchas.
Claude Code specifics:
- This repo **is** a Figma MCPserver. The project-scoped `.mcp.json` launches the local build (`packages/mcp/dist/index.mjs`), so after changing `packages/mcp
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.