# childrentime/reactuse [Health: Active]

**Category:** 🔒 Delivery  
**Repository:** https://github.com/childrentime/reactuse  
**GitHub Stars:** 1052  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/childrentime-reactuse

## Description
MCP server for the ReactUse library — 110+ React Hooks (TypeScript-first, SSR-compatible, tree-shakable). Lets AI assistants discover hook signatures, demos, and usage patterns directly from the docs.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "reactuse": {
    "command": "npx",
    "args": ["-y","@reactuses/mcp@latest"]
  }
}
```

## Documentation

## What childrentime/reactuse MCP server does

The childrentime/reactuse MCP server makes the ReactUse hook library easier for AI assistants to inspect through Model Context Protocol. ReactUse is a collection of more than 100 React Hooks covering browser APIs, state management, DOM elements, effects, sensors, animations, and other common application needs. The MCP interface is intended for documentation discovery rather than for executing application code or changing a project.

An assistant can use the documentation exposed by childrentime/reactuse MCP server to look up hook signatures, review usage patterns, and inspect demos. This can help a developer compare available hooks before adding one to a React or TypeScript codebase.

## How it works

The repository documents an MCP setup based on the `@reactuses/mcp` package. The package runs as a local stdio process, allowing an MCP client to start it and exchange requests through standard input and output. The README does not list individual MCP tool names, so the available operations should be understood as documentation and hook-discovery capabilities rather than a fixed, documented tool inventory.

The underlying ReactUse library is described as TypeScript-supported, tree-shaking friendly, and suitable for server-side-rendered applications including Next.js and Remix. Those are properties of the library being documented; the MCP process itself serves the related reference material to an assistant.

## Setup and configuration

Start the server with `npx` using the package command documented by the project:

```json
{
  "@reactuses/mcp": {
    "command": "npx",
    "args": ["-y", "@reactuses/mcp@latest"],
    "type": "stdio"
  }
}
```

No API key, account, or environment variable is specified in the provided setup. The ReactUse package used in application code is installed separately with `npm i @reactuses/core`; that is the library dependency, not the MCP server package.

## Tools and capabilities

The documented subject areas include:

- Browser hooks such as clipboard, media queries, geolocation, network state, notifications, and window state
- State hooks for toggles, counters, local storage, debouncing, throttling, maps, and related state patterns
- Element hooks for clicks outside elements, drag and drop, visibility, measurements, scrolling, focus, and observers
- Effect hooks for intervals, timeouts, event listeners, mounting, unmounting, and comparison-based effects
- The `useQRCode` integration hook

The MCP documentation is specifically described as providing hook signatures, demos, and usage patterns. It is therefore most suitable for generating implementation guidance, identifying a relevant ReactUse hook, or explaining how a documented hook is intended to be used.

## Limitations and notes

The supplied material does not enumerate the MCP tool names, request schemas, response formats, supported MCP clients, or version compatibility details. It also does not describe remote hosting; the documented configuration runs the package locally through stdio. ReactUse itself is released under the Unlicense, but the excerpt does not separately state a license for every package in the repository.

_Full upstream README: https://allmcps.com/mcp/childrentime-reactuse/readme_