rn-upgrade-helper-mcp
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_helper_urlB | Build the React Native Upgrade Helper URL for a version upgrade. |
| list_changed_filesB | List files changed by React Native Upgrade Helper / rn-diff-purge for a version upgrade. |
| get_file_diffB | Return the Upgrade Helper diff for one changed file. |
| get_upgrade_diffC | Return the full Upgrade Helper diff, optionally filtered by platform. |
| summarize_upgradeB | Summarize the changed areas for a React Native version 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 5 tools
Tools are mostly distinct: URL generation, file listing, per-file diff, full diff, and summary each target different outputs. Minor overlap exists between list_changed_files and get_upgrade_diff (both relate to changes), but descriptions clarify that one returns filenames and the other returns diff content.
All tool names follow a consistent verb_noun pattern using snake_case (get_, list_, summarize_). The verbs are varied but all are imperative and descriptive, making the naming predictable and easy to scan.
With 5 tools, the set is tightly scoped to the domain of React Native upgrade assistance. Each tool serves a distinct purpose without redundancy, and the count is appropriate for the seemingly narrow but useful functionality.
The toolset covers the core workflow: generate a URL, list affected files, inspect individual diffs, obtain the full diff, and get a summary. There are no obvious gaps that would prevent an agent from completing an upgrade assessment.