Skip to main content
Glama
Lizzy223

react-ts-dev-tools

by Lizzy223
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

mcp-dev-tools

An MCP (Model Context Protocol) server that provides AI assistants with tools for React and TypeScript development. It can generate typed form components, explain TypeScript compiler errors, and produce Shadcn UI installation commands.

Tools

generate_react_form

Generates a fully typed React form component using React Hook Form, Zod, and Shadcn UI. The output is ready to drop into a Next.js or Vite project.

Parameter

Type

Required

Description

formName

string

✓

Component name, e.g. UserLoginForm

fields

Field[]

✓

Array of form field definitions (see below)

Field object:

Property

Type

Required

Description

name

string

✓

Key used in form state

label

string

✓

Human-readable label

type

"text" | "email" | "password" | "number" | "select" | "checkbox"

✓

Input type

placeholder

string

—

Placeholder text

description

string

—

Helper text shown below the input

required

boolean

—

Defaults to true

options

string[]

—

Options list for select type

The generated component includes: a Zod schema, inferred TypeScript types, proper default values, and only imports the Shadcn primitives it actually uses.

explain_typescript_error

Analyzes a TypeScript compiler error and returns a structured explanation with recommended fixes.

Parameter

Type

Required

Description

errorMessage

string

✓

Raw TypeScript error output or error code

codeContext

string

—

The problematic code block for additional context

Handles TS2322 (type mismatch), TS2339 (missing property), TS2531 / TS18048 (null / undefined), and general diagnostics.

get_shadcn_install_command

Generates the exact Shadcn CLI command to install a set of UI components, always including the required form and button primitives.

Parameter

Type

Required

Description

components

Array<"form" | "input" | "select" | "checkbox" | "button" | "textarea" | "card" | "dialog">

✓

Components to install

packageManager

"npm" | "pnpm" | "bun" | "yarn"

—

Defaults to "npm"

Related MCP server: Codex Gemini MCP

Requirements

  • Node.js 18+

  • npm / pnpm / bun / yarn

Installation

npm install

Usage

Development (run without compiling)

npm run dev

Production

npm run build
npm start

MCP Inspector (interactive debugging)

npm run inspector

Connecting to an MCP client

Add the following to your MCP client configuration (e.g. Claude Desktop's claude_desktop_config.json):

{
  "mcpServers": {
    "react-ts-dev-tools": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-dev-tools/build/index.js"]
    }
  }
}

Or, if installed globally via npm:

{
  "mcpServers": {
    "react-ts-dev-tools": {
      "command": "mcp-dev-tools"
    }
  }
}

Project structure

mcp-dev-tools/
├── src/
│   ├── index.ts                # Server entry point — registers all tools
│   └── tools/
│       ├── formGenerator.ts    # generate_react_form
│       ├── tsExplainer.ts      # explain_typescript_error
│       └── shadcnInstaller.ts  # get_shadcn_install_command
├── build/                      # Compiled output (generated by tsc)
├── package.json
└── tsconfig.json

Tech stack

Package

Version

Role

@modelcontextprotocol/sdk

^1.29.0

MCP server framework

zod

^4.4.3

Schema validation & parameter definitions

typescript

^7.0.2

Type safety

tsx

^4.23.1

Zero-config TypeScript runner (dev)

ypeScript-Developer-MCP-Server

Available Tools

3 tools
explain_typescript_errorB

Analyzes TypeScript compiler errors and provides clear explanations with fix recommendations.

ParametersJSON Schema
NameRequiredDescriptionDefault
codeContextNoThe problematic TypeScript code block
errorMessageYesThe raw TypeScript error output or error code

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the tool analyzes errors and gives recommendations, but it lacks details on scope (e.g., handling multiple errors), limitations, or whether codeContext is required. The behavior is basic but not fully disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no unnecessary words. It is front-loaded with the core action. However, it could benefit from slight expansion without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of output schema and annotations, the description is minimally complete for a straightforward diagnostic tool. It covers the main purpose but lacks information on return format or usage examples.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. The tool description adds no extra meaning beyond the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's purpose: analyzing TypeScript compiler errors and providing explanations with fix recommendations. It distinguishes itself from sibling tools (get_shadcn_install_command, generate_react_form) which are unrelated tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a TypeScript error is encountered, but it does not explicitly state when to use this tool over alternatives or provide any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

generate_react_formB

Generates fully typed, validated React components using React Hook Form, Zod, and Tailwind CSS.

ParametersJSON Schema
NameRequiredDescriptionDefault
fieldsYesArray of form fields
formNameYesComponent name (e.g., UserLoginForm)

TDQS

B3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It does not disclose side effects like file creation, dependency installation, or any destructive behavior. 'Generates components' is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it omits important details that would justify its brevity. It could be restructured to include key behavioral notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations. The description does not specify what the generated output looks like, where it's saved, or any side effects. Incomplete for a code generation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes descriptions for each parameter. The description adds no additional semantic value beyond the schema, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates fully typed, validated React components using specific libraries (React Hook Form, Zod, Tailwind CSS). It distinguishes from sibling tools (get_shadcn_install_command, explain_typescript_error) which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (e.g., manual implementation, other form generators). The description lacks context about prerequisites or ideal use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_shadcn_install_commandB

Generates the exact Shadcn CLI command to install necessary UI components.

ParametersJSON Schema
NameRequiredDescriptionDefault
componentsYesList of Shadcn UI components needed
packageManagerNoPackage manager to usenpm

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It only states it 'generates' a command but does not disclose that no installation occurs, no side effects, or any prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words; front-loaded with the core action and object.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Minimal description for a simple tool; lacks details about output format, prerequisites, or edge cases, but schema covers parameters adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions, so baseline is 3. The tool description adds no additional meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates the exact Shadcn CLI command for installing UI components, which is specific and distinct from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like generate_react_form or explain_typescript_error; lacks any when-to-use or when-not-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv1.0.0
    • First observedexplain_typescript_error
    • First observedgenerate_react_form
    • First observedget_shadcn_install_command
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

Each tool targets a distinct task: getting shadcn install commands, generating React forms, and explaining TypeScript errors. No overlap in functionality, making selection unambiguous.

Naming Consistency5/5

All three tool names follow a consistent verb_noun pattern (get_, generate_, explain_), making the set predictable and easy to navigate.

Tool Count4/5

Three tools is a reasonable count for a focused set of React+TS utilities, though it leans toward the lower end. Each tool serves a clear purpose within the domain.

Completeness3/5

The tools cover installation, form generation, and error explanation, but miss common development needs like component scaffolding, state management, or testing utilities, leaving notable gaps.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP-Typescribe

    yWorks
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables LLMs to understand and work with TypeScript APIs they haven't been trained on by providing structured access to TypeScript type definitions and documentation.
    30
    46
    MIT

  • Codex Gemini MCP

    donghae0414
    A
    license
    B
    quality
    C
    maintenance
    A TypeScript-based MCP server that provides tools to interact with local Codex and Gemini CLIs via stdio transport. It enables users to execute prompts through the ask_codex and ask_gemini tools, supporting custom models and timeout configurations.
    1
    15
    5
    MIT

  • react-docs

    gaddario98
    F
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing AI coding assistants with documentation and source code for @gaddario98 React packages, including tools for listing packages, retrieving docs and types, and searching source.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lizzy223/ypeScript-Developer-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server