Skip to main content
Glama
muneeb3778

react-dev-mcp

by muneeb3778
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to react-dev-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Workspace Server

      ShayYeffet
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.
      MIT

    • ABSD DevOps MCP Server

      anthonybir
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables secure local filesystem operations and interactive terminal sessions for AI assistants. Provides 12 tools for file management, directory operations, code searching, and running interactive REPLs with security protections.
      11 npm
      MIT

    • MCP Filesystem Server

      pocho23
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure filesystem operations (read, write, list, search, delete) within allowed directories (~/Documents and ~/Downloads), with restrictions such as delete only in Downloads and file size limits.
      12 npm
      MIT

    • Host Terminal MCP

      ankitaa186
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to execute terminal commands on a host machine with configurable, granular permission controls and safety protections. It features multiple security modes, including allowlists and manual approval, to ensure safe command execution within specified directories.
      6
      Apache 2.0

    • Filesystem MCP Server

      Preston-Harrison
      F
      license
      A
      quality
      D
      maintenance
      Enables secure filesystem operations with directory sandboxing and optional read-only mode. Supports file reading/writing, directory management, file searching, and text operations while restricting access to specified directories.
      12
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct file operation: read vs write vs create vs rename vs delete are all clearly separated. search_text and replace_text differ clearly (searching vs modifying content), and run_terminal_command stands apart as the only shell-execution tool. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: read_file, write_file, create_file, create_directory, rename_file, delete_file, list_directory, search_text, replace_text, run_terminal_command. The pattern is perfectly uniform with no deviations.

    Tool Count5/5

    Ten tools is right in the sweet spot for a filesystem/development server. Each tool covers a distinct file, directory, text, or command operation without redundancy, and the count feels neither thin nor bloated for the stated purpose.

    Completeness4/5

    The file/directory CRUD lifecycle is well covered: create, read, write, update (replace_text), rename, delete, and list. Minor gaps exist—such as no append_text or copy_file operation—but agents can compose the existing tools (read + write) to fill most gaps, so no dead ends are present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources