"React" matching MCP servers:

A Model Context Protocol server that provides development and debugging tools for Expo-based React Native applications, enabling developers to manage Expo servers, capture logs, and manipulate project files.

An MCP server that delegates filesystem operations to a specialized React agent, reducing context usage and improving accuracy for AI applications like Claude Code.

Compresses React/Next.js files, HTML, and SVG into a compact JSXN notation optimized for AI assistants, reducing token consumption by ~40%. Provides an MCP server with tools to read, encode, and decode JSXN.

Exposes the agent's sandboxed file tool over stdio so any MCP client can retrieve the contents of a UTF-8 text file inside the working directory, with failures returned as recoverable error strings instead of exceptions. It lets the same ReAct loop swap in-process dispatch for an MCP hop without changing tool signatures.

A terminal-based MCP server that provides tools like web search, URL fetching, note management, and calculations, and connects them to a LangGraph ReAct agent for multi-step tasks.

An MCP server with six tools including web search, URL fetching, math calculation, and note management. Designed for a live-coding demo integrating FastMCP with LangGraph ReAct agents.

Enables rapid creation of new projects from predefined templates including React, Node.js, Django, Flask, and more. Provides comprehensive project scaffolding with file system operations, template management, and command execution capabilities.

A production-grade Model Context Protocol server that enables secure management of context data through a React dashboard, supporting ZIP processing, context approval workflows, and system monitoring.

Official MCP server for UploadKit, the file-uploads platform for developers. Gives Claude Code, Cursor, Windsurf, and Zed first-class knowledge of UploadKit's 40+ open-source React components, Next.js route handler scaffolding, wiring, BYOS (S3/R2/GCS/B2) configuration, and full-text search across 88+ docs pages. Runs locally via npx — no API key, no telemetry, no config.