AGENTS.md examples from real projects

doocsAGENTS.md

md

doocs/md/AGENTS.md

中执行命令 pnpm mcp # 在 @md/mcp-server 中执行命令（render_markdown 等 MCP 工具） pnpm mcp dev # MCP Server 监听模式 ``` `@md/mcp-server` 通过 stdio 暴露 `render_markdown`、`list_themes`、`list_colors` 等工具，配置见 [packages/mcp-server/README.md

darktable-orgAGENTS.md

darktable

darktable-org/darktable/AGENTS.md

when GTK3 has the Wayland backend gui/gtk.c calls into libwayland-client directly to detect server-side decoration support, but gtk+-3.0.pc does not list wayland-client. The symbols were

OpenByteIncReads credentialsAGENTS.md

QuantDinger

OpenByteInc/QuantDinger/AGENTS.md

Repository map - `backend_api_python/`: Flask API, services, trading runtime, migrations, and backend tests. - `mcp_server/`: the tenant-scoped MCP client/server package backed by QuantDinger APIs. - `docs/`: product, architecture, deployment

debeziumAGENTS.md

debezium

debezium/debezium/AGENTS.md

analyze the codebase, DO NOT set up build environments, DO NOT run scripts, or MCP, or skills, DO NOT look things up online, DO NOT make code changes, UNTIL

No other project uses it yet

formbricksReads credentialsAGENTS.md

formbricks

formbricks/formbricks/AGENTS.md

into `useState` or Jotai. The existing server actions wrap service calls and return `{ data }` or `{ error }` consistently; keep that contract when changing them. - MCP tools (`apps/web/modules/mcp`) are thin adapters over

openreplayAGENTS.md

openreplay / mcp_app

openreplay/openreplay/mcp_app/AGENTS.md

OpenReplay MCP App — Agent Guide Reference: https://modelcontextprotocol.github.io/ext-apps/api/documents/Patterns.html --- ## Project Structure ``` server.ts MCP server entry point (stdio transport) lib/ tools.ts All tool registrations (UI + internal) api.ts OpenReplay REST API client

No other project uses it yet

VercelAGENTS.md

portless

vercel-labs/portless/AGENTS.md

change to a CLI command, flag, output, or environment variable must update the MCP tools in `packages/portless/src/mcp.ts` in the same change. `mcp.test.ts` reads `portless --help` and each tool command

AutomatticReads credentialsAGENTS.md

wp-calypso

Automattic/wp-calypso/AGENTS.md

rendering primitives built with WordPress components. Agents Manager consumes it; conversation handling and MCP transport stay in consumers. - **Agenttic** (`packages/agenttic-client`, `packages/agenttic-ui`) — AI agent chat client library and UI components. Also

nearaiReads credentialsAGENTS.md

ironclaw

nearai/ironclaw/AGENTS.md

execution. - Sandboxed extension execution belongs in WASM or a runtime lane; external server integrations belong behind MCP and the network boundary. - Discovery is side-effect-free. Installation, credential binding, activation

nearaiAGENTS.md

ironclaw / tests

nearai/ironclaw/tests/AGENTS.md

before durable storage without retaining inline media/blob base64 | `mcp.rs` | | User-registered and bundled hosted MCP servers register, authenticate, project active, restore, and invoke | `hosted_mcp_registration.rs` | | Web search/fetch runs the real

ChainlitAGENTS.md

chainlit

Chainlit/chainlit/AGENTS.md

over keeping legacy code in place. ## MCP-First Approach (CRITICAL) When available, **ALWAYS** prefer MCP servers over manual alternatives. Use **Context7** for docs/API references, **Serena** for code navigation/refactoring/memory, and **GitHub

tester-armyReads credentialsAGENTS.md

e2e

tester-army/e2e/AGENTS.md

src/agent/` the agent (the `act` executor socket plus the judgment methods), `src/mcp/` the `e2e mcp` server (a live session that rides the `act` socket with a queue executor so every

viarotel-orgAGENTS.md

escrcpy

viarotel-org/escrcpy/AGENTS.md

string | string[]` contract; business code stays untouched across internal changes. - [packages/madb/](../packages/madb/) is an MCP server for AI agent Android device control via ADB and yadb (32 tools

MemTensorReads credentialsAGENTS.md

MemOS

MemTensor/MemOS/AGENTS.md

parsers/` `reranker/` | Provider implementations (`base.py` + `factory.py` + each backend) | | `src/memos/api/` | FastAPI service (routers / handlers / middleware / MCP server) | | `src/memos/configs/` | All pydantic configuration classes (one-to-one with the modules above) | | `src/memos/context/` | Cross

No other project uses it yet

tw93AGENTS.md

Kami

tw93/Kami/AGENTS.md

WeasyPrint-safe. Pure Python, no Node, ships in the package. - `scripts/mcp_server.py` - zero-dependency MCP stdio server exposing `kami_templates` / `kami_doctor` / `kami_render` / `kami_check` / `kami_deliver` / `kami_screenshot

aureuserpAGENTS.md

aureuserp

aureuserp/aureuserp/AGENTS.md

important rather than explaining obvious details. === boost rules === # Laravel Boost - Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them. ## Artisan

mesheryReads credentialsAGENTS.md

meshery

meshery/meshery/AGENTS.md

navigate, snapshot, click, fill forms, run JS, inspect console/network) in place of raw Playwright/chrome-devtools MCP for ad hoc tasks. - Run `quota-axi` to check local agent-provider quota windows before

cocoindex-ioAGENTS.md

cocoindex

cocoindex-io/cocoindex/AGENTS.md

status` to confirm the root is this repo. We register no MCP server on purpose — an `ccc mcp` mode exists, but the CLI costs no context until invoked and behaves

BeehiveInnovationsReads credentialsAGENTS.md

zen-mcp-server

BeehiveInnovations/zen-mcp-server/AGENTS.md

requirements-dev.txt` Also read CLAUDE.md and CLAUDE.local.md if available. ## Project Structure & Module Organization PAL MCP Server centers on `server.py`, which exposes MCP entrypoints and coordinates multi-model workflows. Feature-specific tools

rerun-ioAGENTS.md

rerun

rerun-io/rerun/AGENTS.md

output once the notification arrives. ### Driving a running egui UI (for agents) Two MCP servers let an agent see and click a running UI instead of guessing from code: - `rerun