library_docs
version-correct usage docs for a library, sliced to a token budget.
How to use it
Project documentation lists library_docs for the Cli MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Cli
npx -y @playwright/mcpOther tools in Cli (23)
offline dependency inventory with optional git who-added attribution.
/ retrieveoriginal / compressionstats (with --compress) — shrink a tool output before it enters the context, expand a marker back to the original or just the slice you need, and report what compression saved.
shortest connection between two symbols.
deterministic facts for a node (contract / invariant / characterization).
code map overview: counts, languages, top areas and hubs.
inspect one symbol: signature, callers, callees, area.
Blast radius of changing a symbol
cited standards and practices for a node (OWASP/CWE).
blast radius of a change: dependents, files, covering tests, risk.
code areas (communities) by size.
most-depended-on symbols.
local models on disk (Ollama / LM Studio / gguf).
known vulnerabilities from the last vg scan --vulns: CVE, severity, CVSS, fixed version.
/ memorysave (with --memory) — project-scoped memory shared across your AI agents.
start here: project overview, entry points, where to look first.
find code by meaning: symptoms, relationships, what-breaks-if.
resolve a library to its canonical id and the version your project uses.
Run tests, builds, anything else
Search the code graph — symbols and relations, plus a literal sweep for exact phrases
find a symbol by name or literal string.
which tests cover a symbol.
what breaks if you upgrade a package: major distance, import blast radius, vulns fixed.
who introduced each open vulnerability, exposure windows, CRA remediation metrics.