Ruby Native: MCP server for Rails apps
Ruby Native
The Ruby Native gem's MCP server: the agent checks a Rails app's views and config, tracks builds and prepares an App Store release
- 27 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- submit sends a build to Apple review on behalf of your account and withdraw takes it back
- The CLI token goes to rubynative.com, and the release tools change screenshots, listing and testers in the store
Install
- Works in
Manual install
bundle exec ruby_native mcp installThe README command writes the server into the project's .mcp.json.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- submit sends a build to Apple review on behalf of your account and withdraw takes it back
- The CLI token goes to rubynative.com, and the release tools change screenshots, listing and testers in the store
This is third-party code. Review the repository files before installing.
What it does
Ruby Native turns a Rails app into iOS and Android apps: the HTML from your templates renders as native tab bars, navigation and forms, and builds run in the cloud. The gem adds view helpers, a config/ruby_native.yml file and a CLI for previews and deploys. The built-in MCP server starts with ruby_native mcp. Three tools work on your working copy with no account: check_views finds typos and duplicates in data-native-* attributes, lookup_signals documents each attribute and the gem version it needs, and validate_config shows what the apps will reject in the config. Four tools read your account: status, config_errors, deployed_builds and build_status. The rest prepare a release: icons, screenshots, the store listing, testers and a demo account. The submit tool sends a build to Apple review in two calls: the agent first shows what is going out and only then sends it. withdraw takes a submission out of the queue until Apple approves.
Who it is for. Teams with a Rails product whose customers ask for a mobile app and who want one codebase with no Xcode or Android Studio.
Good fit when
- Rails templates are marked up with data-native-* attributes, and a typo silently breaks a button in the app
- You edit config/ruby_native.yml by hand and want to know what the app will reject when it reads it
- The attribute is right but nothing happens on the phone: the server compares templates with the binary in the store
- A build failed and the agent needs the error text from build_status
- The app is ready to ship and needs screenshots, a store listing and a submission to Apple review
Not a fit when
- The app is not written in Rails: the gem and the server target a Rails app
- You need arbitrary native screens in Swift or Kotlin: Ruby Native renders the HTML of your templates
- You need to work without a paid account: cloud builds and release run on a paid plan, and only the phone preview is free
Example request
Set up Ruby Native in this app, check the views and config, then show which step the App Store release is atMCP
- Transport
- stdio
- Authentication
- API key
Limitations
The gem targets Rails; React and Vue use separate npm packages, @ruby-native/react and @ruby-native/vue. The check_views tool needs the herb gem, as does ruby_native check.
The first three tools stay on your machine, while the rest send your CLI token to rubynative.com. The phone preview starts a Cloudflare tunnel and needs cloudflared. Apple keeps some release steps for a person, so the agent stops at them. Check rubynative.com for plan terms and prices.
How to disable. Remove the ruby-native entry from .mcp.json or uninstall the plugin with claude plugin uninstall. The gem itself stays in the Gemfile and is removed separately along with config/ruby_native.yml.
FAQ
How do I connect the Ruby Native MCP server to Claude Code?
Run bundle exec ruby_native mcp install in the project and the command writes the server into .mcp.json. Another route is the plugin: claude plugin marketplace add ruby-native/gem and claude plugin install ruby-native@ruby-native.
Do I need a Ruby Native account to check views?
No. check_views, lookup_signals and validate_config work on your working copy with no account. The other tools use the token saved by ruby_native login.
Can the agent submit the app to the App Store by itself?
Only in two steps. submit first shows what will go to Apple and sends it after confirmation. withdraw takes the submission back until approval.
Why does nothing happen on the phone when the attribute is right?
The built app may be older than the attribute. The deployed_builds tool shows the version in the store and the signals it does not understand.
How can I see the app before paying?
Run bundle exec ruby_native preview: it starts a Cloudflare tunnel and shows a QR code for the Ruby Native app. The preview is free and needs no account, but cloudflared is required.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
Mobile Device MCP controls iOS and Android: taps, typing, screenshots and the element tree, with several devices at once
An MCP server that installs on a jailbroken iPhone and gives an agent 46 tools: taps, screenshots, OCR, apps, files and logs
A project template and CLI that lets a coding agent build one app natively for iOS, Android and the web from a shared spec.
A Callstack plugin that shows simulators and devices beside the agent chat and lets it control the mobile app.
AutoMobile lets an agent control Android and iOS devices in plain language: explore an app, reproduce bugs and write UI tests
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Ruby Native: MCP server for Rails apps (this card) | yes | API key | 27 | |
| Rails MCP Server | yes | not required | 573 | reads Rails code and routes for development, with no mobile app building |
| Tidewave Rails | yes | not required | 475 | gives the agent access to a running Rails app but does not prepare mobile builds |
| Expo Skills | no | 4,125 | targets React Native and Expo, while this server works with Rails |
README in short
The README covers installing the gem, the generator, a config with tabs and colors, the phone preview and packages for Inertia. A separate section explains the MCP server and tool tables. The site docs are served as Markdown for agents, and an llms.txt exists.