Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/x10send/plex-mcp-server/claude-mdgit clone --depth 1 https://github.com/x10send/plex-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/x10send/plex-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/x10send/plex-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/x10send/plex-mcp-server/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01065 | $0.01065 |
| Opus 5 | $0.00532 | $0.00532 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
plex-mcp-server CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with this repository.
Commands
# Install dependencies
npm ci
# Start dev server (hot reload)
npm run dev
# Run all quality checks (format → lint → typecheck → test+coverage → build)
npm run check
# Run tests only
npm test
# Run a single test file
node --import tsx --test test/library.test.ts
# Run tests with coverage (enforces thresholds)
npm run test:coverage
# Type-check without emitting
npm run typecheck
# Format source
npm run format
# Build to dist/
npm run build
# Build Docker image locally
docker build -t plex-mcp-server .
# Run locally (direct token mode)
docker run --rm \
-e PLEX_URL=http://192.168.1.x:32400 \
-e PLEX_TOKEN=your-token \
-p 3003:3000 \
plex-mcp-server
The npm run check pipeline is the gate: format check → lint → typecheck → test+coverage → build. CI runs the same command.
Architecture
Stateless Fastify HTTP server exposing MCP Streamable HTTP at POST/GET/DELETE /mcp. Each request creates a fresh McpServer + StreamableHTTPServerTransport pair (stateless mode, sessionIdGenerator: undefined).
Token resolution per request: X-Plex-Token header (injected by mcp-edge-gateway) → PLEX_TOKEN env var → 401. The token is never logged.
Module responsibilities:
src/server.ts— entry point only: loads config, callsbuildApp, binds socket, SIGTERM/SIGINT. Excluded from coverage.src/app.ts— Fastify app: health endpoint, MCP route, token resolution, per-request McpServer + transport lifecycle.src/config.ts— env loading, PLEX_URL SSRF validation (blocks public IPs at startup), log level and port validation.src/plex-client.ts— typed Plex HTTP API client. ExportsIPlexClientinterface (used for test mocking) andPlexClientimplementation.PlexApiErrorfor non-2xx responses.src/tools/library.ts— exportsregisterLibraryTools(server, client). Tools:get_libraries,get_library_contents,get_children,get_media_info,get_media_extras.src/tools/discovery.ts— exportsregisterDiscoveryTools(server, client). Tools:search_media,get_genres,get_actors,get_directors,get_collections,get_collection_items,get_related,get_recently_added,get_on_deck,get_watch_history,get_random_items.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 93 lines · 1,065 tokens per session scan A 0c831bfcda19
plex-mcp-server CLAUDE.md is an instructions file published in the GitHub repository x10send/plex-mcp-server (1 stars, last pushed 3d ago), licensed MIT. It adds 1,065 tokens to every session, about $0.0053 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.