React Native Upgrade Helper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_upgrade_infoC | Extract React Native upgrade information between two versions |
| get_file_diffB | Get specific file differences for React Native upgrade |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
Both tools use a consistent 'get_' prefix followed by a noun phrase in snake_case ('upgrade_info', 'file_diff'), establishing a clear naming pattern.
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.
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.