A read-only MCP server that lets AI assistants discover and read the documentation for the 100+ React hooks in the @reactuses/core package.
Look up a specific hook (get_hook): fetch full docs for any hook by name (case-insensitive), including its description, markdown usage/examples, and auto-generated API table (arguments & returns).
Browse all hooks (list_hooks): retrieve every available hook with name, category, description, and docs URL — optionally filtered by one of the five categories (browser, effect, element, state, integrations).
Search hooks (search_hooks): query by name, description, or documentation text, returning relevance-ranked results (up to 50, default 20) with scores to help pick the right hook.
Serve as reference for code generation: gives an assistant the context needed to recommend hooks and write correct, typed usage examples without leaving the MCP client.
Stay side-effect free: all three tools are read-only, idempotent, and closed-world, so they only read bundled documentation and never modify anything.
Sponsoring ReactUse puts your product in front of the React developers who install @reactuses/core every month — your logo right here at the top of the README, and on reactuse.com/sponsor. Live reach:
Related MCP server: daisyui-mcp-server
ReactUse is a comprehensive collection of 100+ essential React Hooks for building modern React applications. Inspired by VueUse, it provides production-ready hooks for browser APIs, state management, sensors, animations, DOM elements, and more.
🎯 100+ Hooks — The most comprehensive React hooks collection
📦 Tree-Shakable — Import only what you need
🔷 TypeScript — Full type definitions for every hook
🖥️ SSR Compatible — Works with Next.js, Remix, and more
📚 Well Documented — Interactive demos for every hook
🤖 MCP Support — AI-powered hook discovery
npm i @reactuses/coreimport { useToggle } from "@reactuses/core";
const Demo = () => {
const [on, toggle] = useToggle(true);
return <button onClick={toggle}>{on ? "ON" : "OFF"}</button>;
};useClipboard, useColorMode, useCookie, useDarkMode, useDocumentVisibility, useEyeDropper, useFavicon, useFileDialog, useFullscreen, useMediaDevices, useMediaQuery, useOnline, usePermission, usePlatform, usePreferredColorScheme, usePreferredContrast, usePreferredDark, usePreferredLanguages, useScreenSafeArea, useScriptTag, useTextDirection, useTitle, useWebNotification, useBroadcastChannel, useEventSource, useFetchEventSource, useGeolocation, useIdle, useKeyModifier, useMobileLandscape, useNetwork, useOrientation, usePageLeave, useSpeechRecognition, useWindowFocus, useWindowScroll, useWindowSize, and more...
useBoolean, useControlled, useCounter, useCycleList, useDebounce, useDebounceFn, useDisclosure, useLocalStorage, useMap, usePrevious, useSessionStorage, useSetState, useThrottle, useThrottleFn, useToggle, and more...
useClickOutside, useDraggable, useDropZone, useElementBounding, useElementByPoint, useElementSize, useElementVisibility, useFocus, useHover, useInfiniteScroll, useIntersectionObserver, useLongPress, useMeasure, useMouse, useMousePressed, useMutationObserver, useResizeObserver, useScroll, useScrollIntoView, and more...
useAsyncEffect, useCustomCompareEffect, useDeepCompareEffect, useEventListener, useInterval, useMount, useRafFn, useTimeout, useTimeoutFn, useUnmount, useUpdate, and more...
useQRCode
If you want to use the MCP (Model Context Protocol) integration with reactuse, you can easily set it up with the following configuration. This allows you to run the @reactuses/mcp utility via npx for enhanced command-line support and automation.
Add the following to your configuration:
"@reactuses/mcp": {
"command": "npx",
"args": ["-y", "@reactuses/mcp@latest"],
"type": "stdio"
}📖 Full Documentation | 📖 LLM-friendly Documentation | 💬 Discord | 🐛 Issues
See the Contributing Guide
See the ChangeLog
This project is heavily inspired by the following awesome projects.
ReactUse is free, released into the public domain under the Unlicense, and maintained in spare time. If it saved you a day of work, consider becoming a sponsor (from $5/month) or buying me a coffee — it keeps the hooks maintained and the docs interactive. 🥰
Fetch full documentation (description, usage example, API table) for a specific @reactuses/core React hook by name.
Inputs: hook_name (required). Returns: api, url, body, name, +2 more
List all available @reactuses/core hooks, optionally filtered by category.
Inputs: category. Returns: hooks, total, category
Search @reactuses/core hooks by name, description, or content. Results are ranked by relevance.
Inputs: query (required), limit. Returns: query, total, results
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clear, distinct purpose: get_hook retrieves details for a specific hook, list_hooks lists all hooks with optional category filter, and search_hooks performs a relevance-ranked search. No ambiguity between them.
All tool names follow a consistent verb_noun pattern (list_hooks, get_hook, search_hooks) using snake_case, making them predictable and easy to understand.
Three tools is minimal but perfectly scoped for the server's purpose: discovering and retrieving information about React hooks. Each tool earns its place without being over- or under-abundant.
The tool set covers the essential operations for a hook library: listing all hooks (with filtering), searching, and fetching full details for a specific hook. There are no obvious gaps given the read-only nature of the domain.
An MCP server that gives your AI access to the source code and docs of all public github repos
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server for agentverse documentation, generated by doc2mcp.
Official Duck Framework MCP server for AI-assisted development and project scaffolding.
