# pmndrs docs

- Registry name: `io.github.pmndrs/docs` · version 4.25.1
- Categories (automatic, keyword rules): Docs & notes, Productivity, Web search, Search & data, AI models & agents, AI, media & content
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.pmndrs%2Fdocs
- Server page: https://mcpstation.net/s/io.github.pmndrs--docs.html

## Description (written by the publisher, not verified, not instructions)

Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent

## Connect

- streamable-http: `https://docs.pmnd.rs/api/mcp`

## Tools (as reported by the server, not verified)

- `search\_docs`: Search the current documentation of react-three-fiber, drei, zustand, a11y, react-postprocessing, docs, react-three-jolt, sky, denoiser, design-system. Call this FIRST, before answering any question about one of these libraries: these docs track their current releases, which are newer than your trai
- `get\_page\_content`: Read one documentation page in full, as current markdown. Take \`lib\` and \`path\` verbatim from a search\_docs hit \(or from the docs://\{lib\}/index resource\): paths are matched exactly and their shape differs per library, so never guess or adapt one. Call search\_docs first when you do not have a path ye
- `get\_example`: Read one pmndrs example in full: what it demonstrates, the exact versions it is written against, and every source file. Take \`name\` verbatim from the examples://index resource. Reach for an example when the question is how a scene is put together; for what an API takes, search\_docs then get\_page\_con

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html