Native_MCP
Provides tools for React Native development, including automatic generation of React Native components with proper structure.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Native_MCP generate a React Native component called LoginScreen"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Native_MCP
A Model Context Protocol (MCP) server for React Native development tools and utilities.
🚀 Overview
Native_MCP is an extensible MCP server that provides tools and utilities for React Native development. It allows AI assistants like Claude to generate React Native components and perform other development tasks through a standardized protocol.
Related MCP server: MCP Python Toolbox
✨ Features
React Native Component Generator: Automatically generate React Native components with proper structure
Extensible Tool System: Add custom tools through a simple plugin architecture
MCP Protocol Compliance: Full compatibility with Model Context Protocol 2025-06-18
Dynamic Tool Loading: Tools are loaded dynamically from the
tools/directory
🛠️ Available Tools
React Native Helper
generate_component: Generate a basic React Native functional component
Input:
component_name(string)Output: Complete React Native component code with View and Text elements
📋 Prerequisites
Python 3.12 or higher
uv package manager
VS Code with Claude extension (for MCP integration)
🔧 Installation
Clone the repository:
git clone https://github.com/ArkVex/Native_MCP.git cd Native_MCPInstall dependencies:
uv syncVerify installation:
uv run mcp_server.py
🚀 Usage
With Claude in VS Code
Configure the MCP server in your Claude settings:
{ "mcpServers": { "native-mcp": { "command": "uv", "args": [ "--directory", "C:\\path\\to\\Native_MCP", "run", "mcp_server.py" ] } } }Start using the tools in Claude:
Ask Claude to "generate a React Native component called LoginScreen"
Claude will use the
generate_componenttool automatically
Manual Testing
You can test the server manually using JSON-RPC:
# Initialize the server
echo '{"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test-client","version":"0.1.0"}},"jsonrpc":"2.0","id":0}' | uv run mcp_server.py
# List available tools
echo '{"method":"tools/list","params":{},"jsonrpc":"2.0","id":1}' | uv run mcp_server.py
# Generate a component
echo '{"method":"tools/call","params":{"name":"generate_component","arguments":{"component_name":"MyButton"}},"jsonrpc":"2.0","id":2}' | uv run mcp_server.py📁 Project Structure
Native_MCP/
├── mcp_server.py # Main MCP server implementation
├── pyproject.toml # Project configuration
├── requirements.txt # Python dependencies
├── tools/ # Tool plugins directory
│ └── react-native-helper/
│ ├── main.py # Tool implementation
│ └── mcp.json # Tool metadata
├── .venv/ # Virtual environment
└── README.md # This file🔌 Adding Custom Tools
To add a new tool to the server:
Create a tool directory:
mkdir tools/my-custom-toolCreate the tool implementation (
tools/my-custom-tool/main.py):def my_function(params): # Your tool logic here result = params.get("input", "default") return {"output": f"Processed: {result}"}Create the tool metadata (
tools/my-custom-tool/mcp.json):{ "name": "my-custom-tool", "entry_point": "main.py", "commands": { "my_function": { "description": "Description of what this tool does", "params": { "input": "string" } } } }Restart the server - tools are loaded automatically
🐛 Troubleshooting
Server Won't Start
Ensure Python 3.12+ is installed
Verify
uvis installed and in your PATHCheck that all dependencies are installed with
uv sync
Tools Not Loading
Verify tool directory structure matches the expected format
Check that
mcp.jsonis valid JSONEnsure the entry point file exists and functions are named correctly
Connection Issues
Verify the MCP server path in your Claude configuration
Check that the server process isn't already running
Review the Claude extension logs for detailed error messages
📖 API Reference
MCP Protocol Methods
initialize: Initialize the server connectiontools/list: Get list of available toolstools/call: Execute a specific toolresources/list: List available resources (currently empty)prompts/list: List available prompts (currently empty)
Tool Response Format
Tools return responses in the MCP standard format:
{
"content": [
{
"type": "text",
"text": "Tool output here"
}
]
}🤝 Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/new-toolMake your changes and add tests
Commit your changes:
git commit -am 'Add new tool'Push to the branch:
git push origin feature/new-toolSubmit a pull request
📝 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
Model Context Protocol for the specification
Anthropic for Claude and MCP support
React Native community for inspiration
📞 Support
If you encounter any issues or have questions:
Check the Troubleshooting section
Search existing GitHub Issues
Create a new issue with detailed information about your problem
Made with ❤️ for the React Native and AI development community
Available Tools
1 toolgenerate_componentC
Generate a React Native component
Inputs: component_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming follows a clear verb_noun pattern.
One tool is too few for a server named 'Native_MCP', which suggests a broader scope related to React Native development. A single component generator feels insufficient for comprehensive coverage.
The tool surface is severely incomplete for React Native development. It only covers component generation, missing essential operations like navigation setup, state management, API integration, or testing tools.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to manage software development projects with complete context awareness and code execution through Docker environments.17 npm4-
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables AI assistants like Claude to perform Python development tasks through file operations, code analysis, project management, and safe code execution.9MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with GitHub repositories, issues, and pull requests.25 npmMIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT