All servers · Docs & notes · Web search · AI models & agents
pmndrs docs
io.github.pmndrs/docs · v4.25.1
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | resources, tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
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
claude mcp add --transport http docs https://docs.pmnd.rs/api/mcp{
"mcpServers": {
"docs": {
"url": "https://docs.pmnd.rs/api/mcp"
}
}
}Tools as reported by the server
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
Repository · Website · JSON · Text for agents · Registry updated 2026-10-13