Skip to main content
Glama
patrickkabwe

React Native MCP Server

by patrickkabwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get-react-native-stable-versionA

Gets the latest stable version of React Native from GitHub releases.

This version represents the most recent production-ready release that has been thoroughly tested and is recommended for use in applications.

The version number follows semantic versioning (e.g. 0.72.0) and excludes any release candidates or beta versions.

This tool is commonly used before planning an upgrade to ensure targeting the latest stable release and must be called before calling get-react-native-diff tool.

The output of this tool will be used as the toVersion parameter in the get-react-native-diff tool.

get-react-native-diffA

Gets the React Native diff between the current version and the user provided version. This diff will show all changes needed to upgrade React Native, including:

  • Package.json dependencies and their versions

  • iOS configuration changes (Podfile, xcodeproj settings)

  • Android configuration (build.gradle, settings.gradle)

  • Project structure changes

  • Binary files that need to be updated

  • Template files modifications

  • Native code changes

  • Troubleshooting steps if any

If no fromVersion is provided, the current version from package.json will be used. The diff follows standard git diff format and should be carefully analyzed to:

  1. Update all dependencies to compatible versions

  2. Apply configuration changes while preserving custom settings and user defined code

  3. Handle binary file updates appropriately

  4. Maintain existing customizations in native code and ts/js files

  5. Update build tools versions (Gradle, CocoaPods, etc) with the correct version from the diff using specific cmds

  6. Preserve any local modifications to template files

  7. Please add the end of the process give instruction on the troubleshooting steps if any(Please detect user's package manager and run the correct cmd):

    • DELETE Pod and Podfile.lock file in iOS folder

    • Run pod install to prevent errors in iOS folder

    • Run this cmd to update android binary ./gradlew wrapper --gradle-version {{CURRENT_GRADLE_VERSION_FROM_DIFF}} —distribution-type {{DISTRIBUTION_TYPE_FROM_DIFF}} in android folder

    • Run {{CURRENT_PACKAGE_MANAGER}} install to install the correct version of the dependencies

YOU MUST call get-react-native-stable-version tool to get the stable version of React Native before calling this tool.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes with no overlap. get-react-native-diff provides detailed upgrade instructions between versions, while get-react-native-stable-version simply retrieves the latest stable version number. An agent would never confuse which tool to use for which task.

Naming Consistency5/5

Both tools follow the exact same naming pattern: get-react-native- followed by a descriptive noun (diff, stable-version). The kebab-case is consistent throughout, and the verb 'get' is used consistently for both retrieval operations.

Tool Count2/5

With only 2 tools, this server feels severely underpowered for a React Native upgrade domain. While the tools work together logically, there are obvious missing operations like applying the diff, checking current version, or handling specific platform configurations separately. The scope suggests more comprehensive tooling would be appropriate.

Completeness2/5

The server is severely incomplete for React Native upgrade workflows. While it provides version information and a diff, there's no tool to actually execute the upgrade steps described in the diff output. Agents would be left with detailed instructions but no automated way to implement them, creating a significant gap in the operational surface.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources