pmndrs docs
io.github.pmndrs/docs · v4.25.1
Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent
MCPremoteno credentialsKnowledge & docsDocuments & PDFFiles & storage
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 84/100
What it does: 3 tools · 3 read, 0 write · Knowledge & docs, Documents & PDF, Files & storage
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +6
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://docs.pmnd.rs/api/mcpTools
3 tools listed at last check
search_docsSearch 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 traiget_page_contentRead 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 yeget_exampleRead 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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.pmndrs/docs)