Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
35 MCP tools give AI agents live Rails schema, routes, models, and conventions.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account crisnahine, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (5.39.1) reached the registry 8 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, AikenDewit
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read, add and schedule your AikenDewit tasks and today's top three from ChatGPT or Claude.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Your coding agent guesses your Rails app. Let it ask.
Website · Quick start · FAQ · What it does · A closer look · How it works · Tools reference · Contributing
An assistant writing Rails code knows what an average Rails app looks like. Yours has its own columns, associations, filters and test setup, and the assistant starts every session with none of that. It writes a migration for a column that exists, calls user.posts when the association is user.articles, scaffolds FactoryBot into a fixture suite, and misses the before_action a parent controller adds. You catch it, fix it, re-prompt, and something next to it breaks.
rails-ai-context gives the assistant 35 tools that read the app itself, over MCP from the AI tool or from the command line. Every answer is read from the app and says how sure it is, and most end with a hint for the next call.
| When | What the assistant gets | A real line from an answer |
|---|---|---|
| It asks about a table | Columns with types, nulls and defaults, the indexes, the model on the table | index_users_on_email on (email) (unique) |
| Before it calls an association | Associations with their options, validations including the implicit ones, enums, scopes, callbacks, concerns | has_many articles dependent: destroy (foreign_key: :author_id, inverse_of: :author) |
| Before it writes an action | The actions, every filter with where it was inherited from, strong parameters, the layout | before authenticate_user! _(from ApplicationController)_ (skipped on: index, show) |
| Before it writes a test | The framework, where the factories or fixtures live, their traits, a template in the app's style | Factories: spec/factories (3 files) |
| It traces a method | The definition and source, what it calls, every caller grouped by file and kind, the tests | app/services/article_publisher.rb (Service) · 11: return false unless @article.publishable? |
| When the app cannot boot | The same tools, from config/routes.rb, the schema dump and the source, saying so | [STATIC] Static mode (static mode requested with --no-boot). Serving static analysis; runtime-only data is marked [UNAVAILABLE]. |
Each line comes from the sample app in this repository, a blog with Devise, an admin namespace, a JSON API, a Sidekiq job and a FactoryBot suite. The website records the whole answers every time it is built, by running the gem at that commit: crisnahine.github.io/rails-ai-context.
The install writes the files each AI tool reads, so the assistant knows the tools exist and how to ask: the MCP config, one root context file with six anti-hallucination rules, and rules that load when a model, a controller or a migration is open. The tools are read-only, the SQL tool runs inside a read-only transaction, and files that hold secrets are never served.
Open your AI tool at the root of your Rails app and paste this. It installs the gem, sets up the AI tool you are in, checks the result and tells you the one step left.
Install the rails-ai-context gem in this Rails app so you can read its schema, models, routes and code through its tools instead of guessing.
ruby -v and bundle exec rails -v. rails-ai-context needs Ruby 3.1+ and Rails 7.0+. If either is older, stop and tell me.bundle add rails-ai-context --group development --version '>= 5.35.0'. If the Gemfile already lists it, run bundle update rails-ai-context --conservative instead. Then run bundle exec rails-ai-context version: it must print 5.35.0 or newer, the first version with the flags used below. If it is older, the Gemfile pins it: change its rails-ai-context line to gem "rails-ai-context", ">= 5.35.0", group: :development and run bundle update rails-ai-context --conservative. If Bundler refuses (a frozen or deployment bundle), run gem install rails-ai-context -v '>= 5.35.0' instead and use rails-ai-context init --tools TOOL --defaults in step 4.bundle exec rails generate rails_ai_context:install --tools TOOL --defaults. If it fails because the app can't boot, run bundle exec rails-ai-context init --tools TOOL --defaults instead; that one reads the source files when the app won't start.bundle exec rails-ai-context tool onboard (or rails-ai-context tool onboard if you used gem install) and check it describes this app.<!-- END install-prompt -->
Rather type it yourself? In the Gemfile:
bundle add rails-ai-context --group development
bin/rails generate rails_ai_context:install --tools claude --defaults
Standalone, with no Gemfile change:
gem install rails-ai-context
rails-ai-context init --tools claude --defaults
As a Claude Code plugin, which adds the MCP server and gives each session the six rules, and writes no context files. It runs the installed gem, so install that first, and run it in the app's folder:
gem install rails-ai-context
claude plugin install rails-ai-context --marketpla
Only the beginning is shown; read the rest in the repo