go-sdk
modelcontextprotocol/go-sdk/AGENTS.md
Packages - `mcp`: The core package defining the primary APIs for constructing and using MCP clients and servers. This is where most logic resides. - `jsonrpc`: Provides the JSON-RPC 2.0 transport
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
modelcontextprotocol/go-sdk/AGENTS.md
Packages - `mcp`: The core package defining the primary APIs for constructing and using MCP clients and servers. This is where most logic resides. - `jsonrpc`: Provides the JSON-RPC 2.0 transport
homarr-labs/homarr/AGENTS.md
maintainer explicitly runs through `homarr-triage` keep that disclaimer as their first line. ## MCP servers The [Homarr Mantine plugin](plugins/homarr-mantine/plugin.json) bundles the UI skill and pinned documentation MCP server. `.agents/plugins/marketplace.json
No other project uses it yet
pollinations/pollinations/AGENTS.md
React frontend - `packages/sdk/` — `@pollinations/sdk` (client + React hooks) - `packages/mcp/` — shared handlers for the hosted stateless MCP server (see `packages/mcp/AGENTS.md`) - `shared/` — auth, registry, IP queue; `shared/registry/` holds model registries - `apps/` — Applications maintained
Steady3 mentions in 2 weeks
No other project uses it yet
chakra-ui/zag/AGENTS.md
pnpm test` | | Start React dev server | `pnpm start-react` (port 3000) | | Start Preact dev server | `pnpm start-preact` (port 5173) | | E2E tests (React) | `pnpm e2e-react` | | E2E tests (Preact) | `pnpm
apache/iggy/AGENTS.md
types (IggyDuration, IggyTimestamp, ...) │ ├── binary_protocol/ Wire format (stable) │ ├── configs/ Config plumbing + ConfigEnv derive │ ├── ai/mcp/ MCP server │ ├── bench/ Benchmark suite │ ├── integration/ Cross-crate integration tests │ ├── simulator/ Deterministic simulator │ ├── consensus/ Raft (Miri
gdamore/tcell/AGENTS.md
gopls` MCP server by default when working on Go code in this repository, unless I explicitly
icip-cas/PPTAgent/AGENTS.md
generation and evaluation library, still shipped in the package and still used for the MCP server entrypoint `pptagent-mcp`. When making changes, treat `deeppresenter` as the primary product surface unless
IsmaelMartinez/teams-for-linux/AGENTS.md
Portfolio dashboard:** https://ismaelmartinez.github.io/repo-butler/ **Consumer guide:** https://github.com/IsmaelMartinez/repo-butler/blob/main/docs/consumer-guide.md ### Querying Reginald (the butler MCP server) To query your repo's health tier, governance findings, and portfolio data from
transformerlab/transformerlab-app/AGENTS.md
local development: ```bash cd lab-sdk && pip install -e . ``` Then restart the API server. This is a common gotcha — the API imports the *installed* `lab` package, not the source tree
totec448-spec/chat-on-steroids/AGENTS.md
browser page | MCP via public tunnel | native UI and conversation state v | MAIN: fiber.js + usage.js Core / Desktop / Plugins | isolated: chatgpt-dom.js + content.js | secret path per surface v server -> registrar -> kernel background.js
facebook/memlab/AGENTS.md
change it (write a leak test scenario, analyze a heap snapshot, set up the MCP server), read [AI.md](./AI.md) and the Agent Skills under [`plugins/memlab/skills/`](./plugins/memlab/skills) instead. ## Repository layout memlab
aldinokemal/go-whatsapp-web-multidevice/AGENTS.md
WhatsApp API server using whatsmeow, Fiber, and SQLite. The Go module and local runtime directory are `src/`. `rest` also mounts MCP at `/mcp` when enabled; both transports share the same
mock-server/mockserver/AGENTS.md
response builder, provider codecs, streaming physics, conversation matchers, isolation, MCP tools, or LLM dashboard | | [docs/code/ai-protocol-mocking.md](docs/code/ai-protocol-mocking.md) | Before modifying MCP/A2A server mocking, SSE/WebSocket/JSON-RPC mock responses, or AI protocol handlers | | [docs/code/llm-codec-fixtures.md](docs/code/llm-codec-fixtures.md
mvanhorn/cli-printing-press/AGENTS.md
runtime walker in `internal/mcp/cobratree/` mirrors the Cobra tree at server start and registers every user-facing command as an MCP tool unless one of these applies: 1. Commands annotated `cmd.Annotations
tfutils/tfenv/AGENTS.md
repos/tfutils/tfenv/...` for operations not covered by high-level `gh` commands. The GitHub MCP server may supplement `gh` where proven reliable, but must never be on the critical path. --- ## Work Type
campfirein/byterover-cli/AGENTS.md
campfirein/brv-transport-client` - Agent pool manages forked child processes per project; task routing in `server/infra/process/` - MCP server in `server/infra/mcp/` exposes tools via Model Context Protocol; `tools/` subdir has dedicated implementations (`brv-query
withcoral/coral/AGENTS.md
entity ID is globally unique. The one exception is Agent authentication at the Organization MCP Endpoint: it finds the Registration by credential verifier alone, because the credential is a secret
anonaddy/anonaddy/AGENTS.md
explicitly requested by the user. === boost rules === # Laravel Boost ## Tools - Laravel Boost is an MCP server with tools designed specifically for this application. Prefer Boost tools over manual alternatives like
dmno-dev/varlock/AGENTS.md
built from `packages/encryption-binary-swift` (darwin) and `packages/encryption-binary-rust` (linux/win32) - `packages/utils`, `packages/plugins` — shared internals - `packages/varlock-docs-mcp` — docs MCP server for external varlock users; do **not** use it to look things up while working
Steady21 mentions in 2 weeks
No other project uses it yet
benjitaylor/agentation/AGENTS.md
Monorepo containing: 1. **npm package** (`package/`) - See `package/AGENTS.md` 2. **Website/docs** (`package/example/`) - See `package/example/AGENTS.md` 3. **MCP server** (`mcp/`, published as `agentation-mcp`) 4. **Agent skills** (`skills/`) ## What is Agentation? A floating
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.