From 5cf8524ae186b0101b6a3a1a52e0142d8983d804 Mon Sep 17 00:00:00 2001 From: Antoine BERNIER Date: Tue, 11 Aug 2026 10:50:53 +0200 Subject: [PATCH] Lead the MCP callout with the claude-code plugin Adding the server on its own leaves the tools sitting there: claude keeps answering react-three-fiber questions from memory, which is the whole problem the server exists to solve. The plugin ships the same server plus the skill that sends it to the docs first, so that is what claude-code users should run. The raw command and the JSON config stay, folded into the details -- they are what every non-claude-code client needs, and dropping them would shut the door on Cursor, Zed and the rest. Co-Authored-By: Claude Opus 5 --- src/app/page.tsx | 23 ++++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/src/app/page.tsx b/src/app/page.tsx index 92d964fe..6c65bc21 100644 --- a/src/app/page.tsx +++ b/src/app/page.tsx @@ -194,13 +194,30 @@ export default function Page() { > MCP-compatible client - , e.g. claude-code : + . +

+ In claude-code, the{' '} + + pmndrs plugin + {' '} + installs this server together with a skill telling Claude to look the docs up rather + than recall an API from memory : +

- {`claude mcp add --transport http pmndrs https://docs.pmnd.rs/api/mcp`} + {`/plugin marketplace add pmndrs/claude-code-plugin +/plugin install pmndrs@pmndrs`}
- Other clients (JSON config) + Server on its own, for any client + + {`claude mcp add --transport http pmndrs https://docs.pmnd.rs/api/mcp`} + {`{ "mcpServers": {