AGENTS.md examples from real projects

pocoprojectAGENTS.md

poco

pocoproject/poco/AGENTS.md

agents/local/`, which git ignores (see [local notes](ai-agents/README.md#local-notes)). MCP server registrations that carry credentials (`.mcp.json`) are never committed. ## Project POCO (Portable Components

maximhqReads credentialsAGENTS.md

bifrost

maximhq/bifrost/AGENTS.md

configuration │ │ ├── plugins.go # Plugin CRUD │ │ ├── cache.go # Cache management │ │ ├── session.go # Auth/session management │ │ ├── health.go # Health checks │ │ ├── mcpserver.go # MCP server (SSE/streamable HTTP) │ │ ├── websocket.go # WebSocket handler │ │ ├── devpprof.go # Pool debug profiler endpoint (~23KB) │ │ └── middlewares.go # Middleware definitions

No other project uses it yet

CloudflareReads credentialsAGENTS.md

vinext

cloudflare/vinext/AGENTS.md

leave known bugs as "follow-ups" — fix them in the same PR. ### Debugging - **Dev server logs**: Run `npx vite dev` in a fixture directory - **RSC streaming issues**: Context is often

No other project uses it yet

MervinPraisonAGENTS.md

PraisonAI

MervinPraison/PraisonAI/AGENTS.md

fine-tuning + agent training in `praisonai-train/`, browser automation in `praisonai-browser/`, MCP server host in `praisonai-mcp/`, sandbox backends in `praisonai-sandbox/`, deployment in `praisonai-deploy/`, integrations/serve/dashboard

No other project uses it yet

miurlaReads credentialsAGENTS.md

morphic

miurla/morphic/AGENTS.md

project supports MCP for enhanced AI assistant integration with Next.js 16. ### Built-in Next.js MCP Server Next.js 16 provides a built-in MCP server at `http://localhost:3000/_next/mcp` when

openstatusHQAGENTS.md

openstatus

openstatusHQ/openstatus/AGENTS.md

connected to this repository and available to coding agents through the [Polylane MCP server](https://mcp.polylane.com/mcp). - When a question involves production behaviour (an error, a spike, a deploy

No other project uses it yet

kunchenguidAGENTS.md

no-mistakes

kunchenguid/no-mistakes/AGENTS.md

parser; the reviewer writes with its own file tools, so there is deliberately no MCP server. That package therefore owns `AppendAnswer` (the daemon's answer handler) and NO question writer

tsparticlesAGENTS.md

tsparticles

tsparticles/tsparticles/AGENTS.md

exec nx test`) - avoids using globally installed CLI - You have access to the Nx MCP server and its tools, use them to help the user - For Nx plugin best practices

No other project uses it yet

strands-agentsAGENTS.md

sdk-python

strands-agents/sdk-python/AGENTS.md

/AGENTS.md ├── strands-ts/ # TypeScript SDK (npm workspace) — see strands-ts/AGENTS.md ├── strands-mcp/ # MCP server with Strands docs for coding agents (hatch) ├── site/ # Documentation site (Astro) — see site/AGENTS.md ├── team/ # Governance

No other project uses it yet

strands-agentsAGENTS.md

sdk-python / strands-py

strands-agents/sdk-python/strands-py/AGENTS.md

while the SDK was *running* that an operator would want in their logs (an MCP server failed to start, a tool failed to load, a store write failed). These

GoogleReads credentialsAGENTS.md

adk-go

google/adk-go/AGENTS.md

auth providers for outbound requests - `agentregistry/` Client for Google Cloud Agent Registry (A2A agents, MCP servers, models) - `plugin/` Cross-cutting lifecycle hooks; `plugin/agentanalytics` is a separate module - `server/` HTTP servers

No other project uses it yet

strands-agentsAGENTS.md

harness-sdk / strands-py

strands-agents/harness-sdk/strands-py/AGENTS.md

while the SDK was *running* that an operator would want in their logs (an MCP server failed to start, a tool failed to load, a store write failed). These

No other project uses it yet

apacheAGENTS.md

shenyu

apache/shenyu/AGENTS.md

dubbo, grpc, spring-cloud, sofa, tars, websocket, mqtt...), `-security`, `-logging`, `-cache`, `-fault-tolerance`, `-ai`, `-mcp-server`, etc. A plugin is activated by adding its starter to the bootstrap pom. - **`shenyu

rikkahubAGENTS.md

rikkahub

rikkahub/rikkahub/AGENTS.md

conversation is persisted it also holds a `ConversationConfig` snapshot (chat model, reasoning level, search, MCP servers, workspace, skills) taken from the assistant; from then on chat-page changes to those

No other project uses it yet

ever-coAGENTS.md

ever-gauzy

ever-co/ever-gauzy/AGENTS.md

affected`) instead of using the underlying tooling directly - You have access to the Nx MCP server and its tools, use them to help the user - When answering questions about

Gentleman-ProgrammingAGENTS.md

gentle-ai

Gentleman-Programming/gentle-ai/docs/agents.md

configuration, so Gentle AI makes no Conductor-specific writes: it does not install skills, MCP servers, or system prompt files for Conductor — configure those through Claude Code instead

storytoldAGENTS.md

effectcraft

storytold/effectcraft/AGENTS.md

crates/engine`): id, label, menu path, shortcut, params, enabled(), run(). UI, CLI, control channel and MCP dispatch by id. - **Everything is agent-drivable:** every interactive widget registers an automation

No other project uses it yet

storytoldAGENTS.md

effectcraft

storytold/effectcraft/docs/agents.md

macOS with the CLI unzipped onto PATH claude mcp add effectcraft -- effectcraft-cli mcp ``` The server speaks JSON-RPC 2.0 over stdio, one message per line, and supports MCP protocol

No other project uses it yet

meshtasticAGENTS.md

firmware

meshtastic/firmware/AGENTS.md

embedded codebase targeting ESP32 / nRF52 / RP2040 / STM32WL / Linux-Portduino LoRa mesh radios. The Python MCP server that AI agents use to flash, configure, and test connected devices now lives

llamastackReads credentialsAGENTS.md

llama-stack

llamastack/llama-stack/AGENTS.md

through a provider architecture. ## Repository Layout ```text src/ogx/ # Server implementation core/ # Request routing, server, storage providers/ inline/ # Built-in providers (responses, eval, vector_io, etc.) remote/ # Remote provider adapters (OpenAI