pmndrs docs: react-three-fiber documentation over MCP
pmndrs docs
A key-free remote MCP server that gives an agent the docs and examples of react-three-fiber, drei, zustand and jotai page by page
- 120 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The server gives the agent public docs and examples read-only and asks for no credentials
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/pmndrs-docsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The server gives the agent public docs and examples read-only and asks for no credentials
This is third-party code. Review the repository files before installing.
What it does
pmndrs docs is an MDX documentation generator that builds docs.pmnd.rs. The same site serves its content to agents over MCP: one address, `https://docs.pmnd.rs/api/mcp`, uses Streamable HTTP and covers every library in the pmndrs ecosystem. The `llms-full.txt` file is too big to paste in whole. So an agent first reads a library index, the resource `docs://{lib}/index` with one line per page, and then requests the one page it needs with the tool `get_page_content`, passing `lib` and `path`. The resource `docs://pmndrs/manifest` lists the libraries served. The server also serves the examples gallery: the resource `examples://index` and the tool `get_example`, which returns an example's source, live URL, asset attribution and dependency versions. Libraries that publish `llms-full.txt` join through a pull request to the repository.
Who it is for. Developers on react-three-fiber, drei, zustand and jotai who ask an agent about the API or want a scene built from ready examples.
Good fit when
- The agent invents props that drei does not have and needs the real documentation page
- You want to know how a zustand hook works, for example with TypeScript
- You need an example of an effect such as caustics or refraction with its source code
- You want pmndrs docs in Claude Code through a single plugin
- A library author wants agents to read their docs over MCP
Not a fit when
- You need docs for libraries outside the pmndrs ecosystem: the server serves only those in its manifest
- You need an exact signature reference for your version: examples pin their own dependency versions
- You work offline: the server is remote
Example request
How do I use instances from drei in react-three-fiber? Fetch the docs page and show an example with a link to the source.MCP
- Transport
- http
- Authentication
- not required
Limitations
The server serves only libraries listed in its manifest, and a library gets there by publishing `llms-full.txt` and being flagged in `src/app/page.tsx`. Pages are fetched at call time and revalidated every five minutes.
Each example pins its own dependency versions. For a current API signature the author advises checking the docs and not the example. An example suits a "how is it put together" question, and a docs page suits "what does the API take".
The server is remote, so an agent cannot reach it without a network. The plugin install works in Claude Code; for other clients take the JSON config from the site home page.
How to disable. Remove the server from the MCP client or disable the plugin with `/plugin uninstall pmndrs@pmndrs` in Claude Code. The service issues no keys.
FAQ
Does the server need a key?
No, it is open. The MCP registry lists it as a remote server with streamable-http transport and no environment variables.
Which libraries does it serve?
Every library badged MCP on docs.pmnd.rs, including react-three-fiber, drei, zustand and jotai. The current list is in the resource `docs://pmndrs/manifest`.
How do I connect it in Claude Code?
Through the plugin: `/plugin marketplace add pmndrs/claude-code-plugin`, then `/plugin install pmndrs@pmndrs`.
How is this better than llms.txt?
`llms-full.txt` is too big to paste into context. MCP lets the agent read the index and fetch only the page it needs.
How can I test the server before connecting?
Run `npx -y @modelcontextprotocol/inspector`, add the server manually with transport `streamable-http` and the address `https://docs.pmnd.rs/api/mcp`, and preview the react-three-fiber index.
Discussion
No questions or reviews yet.
Related
MCP serversAn agent gets the MDMA spec, prompts and validation so it can answer with forms, tables and approvals right inside Markdown
Remote MCP server with Farm.js documentation: pages, sections, code examples and config options for an agent to search
The @microcharts/mcp server: an agent picks from 106 tiny React charts, gets ready props and receives SVG with alt text
The Arc UI MCP server: an agent searches animated React components, reads docs and props and gets the shadcn install command.
An agent inspects a live Three.js scene, tries material and light tweaks in the browser and writes the accepted ones into source.
ReactUse MCP: React hooks reference
ReactUse MCP
ReactUse MCP server: the agent finds the right React hook and reads its description, example and API table straight from the library
README in short
The README covers the generator: reading docs with `npx @pmndrs/docs`, searching pages and building HTML or a static site. The agents section explains publishing `llms.txt`, the MCP server, the examples and how a new library joins.