pmndrs docs is an MCP server published by io.github.pmndrs, hosted at docs.pmnd.rs. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 3 tools, including search_docs, get_page_content, get_example.
Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| lib | string | Search this library only. Leave out to search all of them. |
| query * | string | What to look for: a component, hook, prop or concept, in a few words (e.g. "useFrame", "instanced mesh", "persist middleware"). Every term has to match. |
{
"name": "search_docs",
"title": "Search Docs",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"lib": {
"enum": [
"react-three-fiber",
"drei",
"zustand",
"a11y",
"react-postprocessing",
"docs",
"react-three-jolt",
"sky",
"denoiser",
"design-system"
],
"type": "string",
"description": "Search this library only. Leave out to search all of them."
},
"query": {
"type": "string",
"minLength": 1,
"description": "What to look for: a component, hook, prop or concept, in a few words (e.g. \"useFrame\", \"instanced mesh\", \"persist middleware\"). Every term has to match."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| lib * | string | The library name, as search_docs returned it |
| path * | string | The page path, as search_docs returned it (e.g. /api/hooks/use-frame) |
{
"name": "get_page_content",
"title": "Get Page Content",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"lib",
"path"
],
"properties": {
"lib": {
"enum": [
"react-three-fiber",
"drei",
"zustand",
"a11y",
"react-postprocessing",
"docs",
"react-three-jolt",
"sky",
"denoiser",
"design-system"
],
"type": "string",
"description": "The library name, as search_docs returned it"
},
"path": {
"type": "string",
"description": "The page path, as search_docs returned it (e.g. /api/hooks/use-frame)"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | An example name taken verbatim from the examples://index resource |
{
"name": "get_example",
"title": "Get Example",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "An example name taken verbatim from the examples://index resource"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.