pmndrs docs

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

我该使用它吗

质量与安全性

A
描述质量
100%
模式完整度
100%
命名质量
100%
投毒风险
100%
权限匹配度
100%
协议合规性
100%

基于对工具定义和协议合规性的自动分析。

上下文开销

~703token 数(工具定义)
~1.2 KB典型响应大小
对注意力有中等影响(占 128k 上下文窗口的 0.55%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

{
  "mcpServers": {
    "docs": {
      "url": "https://docs.pmnd.rs/api/mcp"
    }
  }
}

远程端点

https://docs.pmnd.rs/api/mcpstreamable-http

它能做什么

工具清单

工具(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.

输入模式

{
  "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.

输入模式

{
  "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.

输入模式

{
  "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#"
}

社区

评价此服务器

证据

最近观测

已验证未记录版本3 个工具