Mcp Usehooks

Created By
packages10 months ago
A Model Context Protocol (MCP) server for accessing React hooks from usehooks.io with enhanced formatting options and caching.
Overview

What is Mcp Usehooks?

Mcp Usehooks is a Model Context Protocol (MCP) server designed to provide access to a collection of production-ready React hooks from usehooks.io, featuring enhanced formatting options and caching capabilities.

How to use Mcp Usehooks?

To use Mcp Usehooks, you can initialize it in your React project using the command: npx -y mcp-usehooks. You can then utilize the CLI tool to add hooks, list available hooks, and get detailed information about specific hooks.

Key features of Mcp Usehooks?

  • 30+ Production-Ready Hooks: A comprehensive library of hooks that are carefully crafted and tested for production use.
  • Zero Configuration: Works seamlessly out of the box with any React project.
  • CLI Tool: A powerful command-line interface for easy hook management.
  • Smart Search: Quickly find hooks by name, description, or category.
  • Type Safe: Full TypeScript support with detailed type definitions.
  • Customizable: Flexible configuration options to suit various use cases.

Use cases of Mcp Usehooks?

  1. Simplifying state management in React applications.
  2. Enhancing user experience with device APIs like geolocation and media session.
  3. Streamlining the development process with reusable hooks and a CLI tool.

FAQ from Mcp Usehooks?

  • What types of hooks are available?

The library includes hooks for state management, sensors, device APIs, utilities, lifecycle management, network requests, and authentication.

  • Is there documentation available?

Yes! Comprehensive documentation is provided for each hook, including examples and best practices.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and guidelines for adding new hooks are provided in the documentation.

Server Config

{
  "mcpServers": {
    "usehooks": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-usehooks"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
packages
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago