# pmndrs docs

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

- name: io.github.pmndrs/docs
- version: 4.25.1
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.pmndrs%2Fdocs
- tools: https://api.protogrid.dev/v1/servers/io.github.pmndrs%2Fdocs/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "docs": {
      "type": "http",
      "url": "https://docs.pmnd.rs/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-97% +updated-6d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 3 of 3 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 675 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- fail `stability.rug_pull`: 2 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 675 tokens to load them all
- tool set hash: 070605ad8671205a57c422cbb5ffe41e
- tools last changed: 2026-10-13T13:43:47.857Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.pmndrs/docs.svg)](https://protogrid.dev/servers/io.github.pmndrs/docs)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-13 `get_example` changed (inputSchema)
- 2026-10-13 `get_page_content` changed (inputSchema)
- 2026-10-13 `search_docs` changed (inputSchema)
- 2026-10-07 `get_page_content` changed (inputSchema)
- 2026-10-07 `search_docs` changed (description, inputSchema)
  - before: Search the current documentation of react-three-fiber, drei, zustand, a11y, react-postprocessing, docs, react-three-jolt, sky, denoiser. Call this FIRST, before answering any question about one of these libraries: these docs track their current releases, which are newer than your training data, and their APIs changed across major versions (react-three-fiber v9, drei v10, zustand v5 each broke things), so an answer from memory is likely stale. Returns the 10 best-matching pages, best first, each with the lib and path to pass to get_page_content.
  - after: 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 training data, and their APIs changed across major versions (react-three-fiber v9, drei v10, zustand v5 each broke things), so an answer from memory is likely stale. Returns the 10 best-matching pages, best first, each with the lib and path to pass to get_page_content.
- 2026-10-02 `get_example` changed (description, annotations) **meaning changed**
  - before: Get a pmndrs example in full: what it demonstrates, the versions it is written against, and every source file.
  - after: 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_content.
- 2026-10-02 `get_page_content` changed (description, inputSchema, annotations) **meaning changed**
  - before: Get surgical content of a specific page.
  - after: 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 yet.
- 2026-10-02 `search_docs` added
  - Search the current documentation of react-three-fiber, drei, zustand, a11y, react-postprocessing, docs, react-three-jolt, sky, denoiser. Call this FIRST, before answering any question about one of these libraries: these docs track their current releases, which are newer than your training data, and their APIs changed across major versions (react-three-fiber v9, drei v10, zustand v5 each broke things), so an answer from memory is likely stale. Returns the 10 best-matching pages, best first, each with the lib and path to pass to get_page_content.

Full history: https://api.protogrid.dev/v1/servers/io.github.pmndrs%2Fdocs/changes

## Remotes

- https://docs.pmnd.rs/api/mcp (streamable-http, auth none, reachable true, uptime30d 0.9705882)

## Packages

_none_

## Tools (3)

- `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_content.
- `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 yet.
- `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 training data, and their APIs changed across major versions (react-three-fiber v9, drei v10, zustand v5 each broke things), so an answer from memory is likely stale. Returns the 10 best-matching pages, best first, each with the lib and path to pass to get_page_content.