Skip to main content
Glama
KalinYorgov

React Native Upgrade Helper MCP Server

by KalinYorgov
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

React Native Upgrade Helper MCP Server

A Model Context Protocol (MCP) server that automates the React Native Upgrade Helper website to extract upgrade information between React Native versions.

What It Does

This MCP server uses Playwright to automatically:

  1. Fill out the React Native Upgrade Helper form with your version details

  2. Extract comprehensive upgrade information including file diffs

  3. Return structured JSON data that AI assistants can use to help with React Native upgrades

Related MCP server: React Native MCP Server

Installation

  1. Clone and install dependencies:

git clone <repository-url>
cd react-native-upgrade-helper-mcp
npm install

  1. Install Playwright browser:

npx playwright install chromium

  1. Build the project:

npm run build

Configuration

Add this server to your MCP client configuration:

Claude Code

Add to ~/.config/claude-code/mcp_servers.json:

{
  "mcpServers": {
    "react-native-upgrade-helper": {
      "command": "node",
      "args": ["/absolute/path/to/react-native-upgrade-helper-mcp/dist/index.js"]
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "react-native-upgrade-helper": {
      "command": "node",
      "args": ["/absolute/path/to/react-native-upgrade-helper-mcp/dist/index.js"]
    }
  }
}

Cursor

Add to your MCP settings:

{
  "servers": {
    "react-native-upgrade-helper": {
      "command": "node",
      "args": ["/absolute/path/to/react-native-upgrade-helper-mcp/dist/index.js"]
    }
  }
}

Important: Replace /absolute/path/to/react-native-upgrade-helper-mcp/ with the actual absolute path to this project directory.

Usage

The server provides two tools:

1. get_upgrade_info

Get comprehensive upgrade information between React Native versions.

Parameters:

  • fromVersion (required): Source React Native version (e.g., "0.70.14")

  • toVersion (required): Target React Native version (e.g., "0.74.0")

  • packageName (optional): Package name (default: "com.example.app")

  • projectName (optional): Project name (default: "ExampleApp")

Example:

@react-native-upgrade-helper get_upgrade_info fromVersion=0.70.14 toVersion=0.74.0

2. get_file_diff

Get specific file differences for the upgrade.

Parameters:

  • fromVersion (required): Source React Native version

  • toVersion (required): Target React Native version

  • fileName (required): Specific file to get diff for (e.g., "package.json")

  • packageName (optional): Package name (default: "com.example.app")

  • projectName (optional): Project name (default: "ExampleApp")

Example:

@react-native-upgrade-helper get_file_diff fromVersion=0.70.14 toVersion=0.74.0 fileName=package.json

Example AI Prompts

Once configured, you can ask your AI assistant:

  • "Help me upgrade my React Native app from 0.70.14 to 0.74.0. What changes do I need to make?"

  • "Show me the specific changes needed for package.json when upgrading to RN 0.74.0"

  • "What are the breaking changes when upgrading from React Native 0.70 to 0.74?"

Output Format

get_upgrade_info returns:

{
  "fromVersion": "0.70.14",
  "toVersion": "0.74.0",
  "packageName": "com.example.app",
  "projectName": "ExampleApp",
  "url": "https://react-native-community.github.io/upgrade-helper/",
  "summary": "Upgrade summary information",
  "breakingChanges": ["Breaking change descriptions"],
  "fileChanges": [
    {
      "fileName": "package.json",
      "changeType": "modified",
      "hasChanges": true,
      "content": "diff content..."
    }
  ],
  "totalFiles": 15,
  "modifiedFiles": 12,
  "addedFiles": 2,
  "deletedFiles": 1
}

get_file_diff returns:

{
  "fromVersion": "0.70.14",
  "toVersion": "0.74.0",
  "fileName": "package.json",
  "changeType": "modified", 
  "diff": "actual diff content...",
  "found": true
}

Development

# Run in development mode
npm run dev

# Build for production
npm run build

# Test the server manually
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}' | node dist/index.js

Troubleshooting

Playwright issues: Ensure Chromium is installed:

npx playwright install chromium

Permission errors: Make sure the script is executable:

chmod +x dist/index.js

Path issues: Always use absolute paths in MCP configuration files.

Network timeouts: The server waits 15 seconds for page loads. For slower connections, modify the timeout in src/index.ts.

License

MIT License

Available Tools

2 tools
get_file_diffGet Specific File DiffB

Get specific file differences for React Native upgrade

ParametersJSON Schema
NameRequiredDescriptionDefault
fileNameYesSpecific file to get diff for (e.g., "package.json", "android/build.gradle")
toVersionYesTarget React Native version
fromVersionYesSource React Native version
packageNameNoPackage namecom.example.app
projectNameNoProject nameExampleApp

TDQS

B3.4/5.0
Behavior2/5

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. However, it only states 'Get specific file differences' without explaining what the diff looks like, whether it's read-only, or any potential side effects. This is a significant gap in a tool with no annotation support.

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?

The description is a single, front-loaded sentence that states the purpose without any filler or redundancy. It is appropriately concise for its simplicity.

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?

With no output schema and no annotations, the description needs to explain return values and behavioral context, but it does not. Given the tool has 5 parameters and one sibling, the description is too lean to be considered adequately complete, especially since it doesn't clarify what the diff output looks like or how it differs from get_upgrade_info.

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?

The schema provides 100% coverage with descriptions for all parameters, so the schema does the heavy lifting. The description adds no additional parameter information beyond what the schema already offers. Baseline of 3 is appropriate when schema coverage is high.

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 uses a specific verb 'get' and resource 'specific file differences', clearly indicating it retrieves diffs for a particular file. The phrase 'for React Native upgrade' adds context, and it distinguishes from the sibling tool get_upgrade_info, which presumably handles general upgrade information.

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 in the React Native upgrade process, but it does not explicitly state when to use this tool versus get_upgrade_info or any exclusions. It provides minimal usage context but no direct alternatives or when-not-to-use guidance.

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

get_upgrade_infoGet React Native Upgrade InformationC

Extract React Native upgrade information between two versions

ParametersJSON Schema
NameRequiredDescriptionDefault
toVersionYesTarget React Native version (e.g., "0.74.0")
fromVersionYesSource React Native version (e.g., "0.70.14")
packageNameNoPackage name for the projectcom.example.app
projectNameNoProject nameExampleApp

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. 'Extract' implies a read-only operation, but the description does not explicitly state side effects, required permissions, rate limits, or what the output represents. The agent is left guessing about the tool's behavior.

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 sentence with no fluff, making it concise and easy to parse. It front-loads the primary action and resource. However, it is perhaps too terse given the tool's complexity, though this does not hurt conciseness itself.

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?

The description is not complete for a tool with 4 parameters, no annotations, and no output schema. It fails to explain what 'upgrade information' entails, what the return format is, or any prerequisites. An agent cannot fully understand the tool's behavior or expected results from the description alone.

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 description coverage is 100%, so all parameters are already documented in the input schema. The description adds minimal semantic value beyond restating 'between two versions' which corresponds to the fromVersion and toVersion parameters. The optional parameters packageName and projectName are not mentioned in the description but are fully covered in the schema.

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

Purpose4/5

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

The description uses a specific verb ('Extract') and names the resource ('React Native upgrade information') with the scoping 'between two versions'. It is clear about the core function, though it does not explicitly differentiate from the sibling get_file_diff, which likely serves a different purpose.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no context about when it is appropriate to invoke. There is no mention of when not to use it or how it relates to get_file_diff.

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. 2 tool updatesv1.0.0
    • First observedget_file_diff
    • First observedget_upgrade_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have distinct purposes: one provides high-level upgrade information between versions, the other retrieves specific file diffs. No overlap or confusion in their intended use.

Naming Consistency5/5

Both tools use a consistent 'get_' prefix followed by a noun phrase in snake_case ('upgrade_info', 'file_diff'), establishing a clear naming pattern.

Tool Count3/5

With only two tools, the server feels minimal for the stated purpose of upgrade assistance. While it's a focused set, it's on the borderline of being too thin, as a typical upgrade helper might require more granular operations.

Completeness2/5

The toolset lacks a way to discover which files changed between versions, making get_file_diff difficult to use without external knowledge. Additionally, there is no tool to list available React Native versions, creating a notable gap that could cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

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/KalinYorgov/RN-upgrade-helper-MCP'

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