pmndrs docs
Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent
Sollte ich dies verwenden
Qualität und Sicherheit
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"docs": {
"url": "https://docs.pmnd.rs/api/mcp"
}
}
}Remote-Endpunkte
https://docs.pmnd.rs/api/mcpstreamable-httpWas es kann
Tool-Inventar
Tools (3)
🟢search_docs(query, lib)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"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."
},
"lib": {
"type": "string",
"enum": [
"react-three-fiber",
"drei",
"zustand",
"a11y",
"react-postprocessing",
"docs",
"react-three-jolt",
"sky",
"denoiser"
],
"description": "Search this library only. Leave out to search all of them."
}
},
"required": [
"query"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_page_content(lib, path)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"lib": {
"type": "string",
"enum": [
"react-three-fiber",
"drei",
"zustand",
"a11y",
"react-postprocessing",
"docs",
"react-three-jolt",
"sky",
"denoiser"
],
"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)"
}
},
"required": [
"lib",
"path"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_example(name)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "An example name taken verbatim from the examples://index resource"
}
},
"required": [
"name"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Nachweis