conventions — lives in **@AGENTS.md**. Read it first.
## Claude-specific notes
- This is an IMAP/SMTP **MCPserver** (TypeScript, ESM). It uses **`imapflow`**
for IMAP and **`nodemailer`** for SMTP. (It does
installer copies the skills, update command shim, agents, rules, hooks, knowledge, bypass tables, MCP runtime, and generated settings. It merges `.mcp.json` and `.claude/settings.json` instead of overwriting unrelated config.
4. After
CLAUDE.md
XC-MCP is an MCPserver exposing `xcodebuild`, `simctl` and `idb` as 77 tools, built to keep Xcode's
enormous output inside a model's context. Published
This project is about developing the mcp_server typo3 extension, that allows someone without technical knowledge to edit content using LLM's.
- Run the tests using `composer test`. Test must
existing failures — if tests are failing, fix them.
## Running the server
```
uv tool run --python 3.12 build123d-mcp
```
Communicates over stdio (MCP SDK v2 `MCPServer`). When configuring an MCP client
Power Platform MCPServer — Claude Code Instructions
## The 6-Phase Flow Workflow
**ALWAYS follow this workflow when users want to create, build, or modify a Power Automate flow:**
### Phase
system-maintenance | [2389-research/remote-system-maintenance](https://github.com/2389-research/remote-system-maintenance) | Linux system diagnostics and maintenance via SSH/tmux |
### MCPServers
| Server | Repo | Description |
|--------|------|-------------|
| agent-drugs | [2389-research/agent-drugs](https://github.com/2389-research/agent-drugs) | Digital drugs that modify
full** test suite, so commits are slow but pre-verified.
## Architecture
An MCP stdio server wrapping the Open Library HTTP API. Three layers:
**`src/index.ts`** — the `OpenLibraryServer` class. Builds
notification first.
- **Bundled tools** under `Contents/Helpers`: the `keepresso` CLI and the
`keepresso-mcp` stdio MCPserver (both drive automation leases). A
ready-to-install agent skill ships under
`Contents/Resources/AgentSkill/keep-awake`.
- **Localization
Open Reality stack (`reality-opened/openreality`),
three components in one repo:
- `mcp/`: the MCPserver (npm `openreality-mcp`). Developed HERE directly; an
all-plugin cordis app. Read `mcp/CLAUDE.md` before changing
public `reality-opened/openreality` monorepo
(npm `openreality-mcp`): Open Reality OS as MCP tools. An **all-plugin [cordis](https://github.com/cordiverse/cordis)
app**. Read the Architecture section of [README.md](README.md) before
against the live MCP catalog (the ` .json` schema files exposed by the connected MCPserver). The MCP descriptor wins over codebase function names, prior skill content, or memory.
- **Allowed Hyper
CLIs (Claude Code, OpenCode, Codex) using a persistent SQLite state store, exposed via an MCPserver and CLI.
## Build & Development Commands
A `Makefile` wraps the common `pnpm` scripts — prefer
manifest are silently ignored by
current loaders — the sync test rejects them. The kb.* MCPserver is
deployment config (`openclaw mcp add vouch -- vouch serve`); the trust
boundary lives
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.