OpenApps

BuiltOnRails MCP server — tools & history

BuiltOnRails MCP server: observed open status, tool schemas, linked apps and version history.

BuiltOnRails

Endpoint: https://builtonrails.com/mcp

Observed status: open. Checked: 2026-10-12T05:09:09+00:00.

Linked apps

  • BuiltOnRails

    Stack intelligence from real production Rails apps. Compare gems, scan a Gemfile. No API key.

Observed tools

  • admin_changelog — ADMIN ONLY - the feature/changelog ledger over MCP. Requires an admin Bearer token. This is the source of truth for what shipped - log an entry here right after shipping something instead of hand-editing docs/changelog.md, so the record can't drift from reality. Entries left un-digested automatically get folded into the next Monday promotional digest (see admin_newsletters). Actions: 'list' shows recent entries (filter by category or digest status); 'create' logs a new entry (title, description, category, optional version); 'update' edits an entry by id; 'destroy' removes one.
  • admin_moderation — ADMIN ONLY - moderate BuiltOnRails listings over MCP. Requires an admin Bearer token (Authorization header). Actions: 'pending' lists products awaiting review; 'approve' / 'reject' run the review lifecycle on a product slug; 'feature' / 'unfeature' toggle homepage featuring; 'stats' returns moderation counts. Params: action (required); slug (required for approve/reject/feature/unfeature); limit (pending only, default 10, max 50).
  • admin_news — ADMIN ONLY - batch-review the curated news queue (ContentItems behind /daily and the newsletter) over MCP. Requires an admin Bearer token. Actions: 'queue' lists items awaiting review (filter by feed name or search term); 'select' / 'reject' batch-review by ids (array); 'stats' returns queue counts by status and top feeds. Typical flow: queue -> read titles -> select the good ids, reject the noise, in batches.
  • admin_newsletters — ADMIN ONLY - queue and send promotional/update newsletters over MCP. Requires an admin Bearer token. Each newsletter is only ever delivered once per subscriber, even across retries. The 'all_subscribed' segment is additionally throttled: it skips anyone who got a newsletter in the last 7 days or any email at all in the last 2 days, so promos never stack on top of other mail. Leaving an 'all_subscribed' newsletter as a draft (don't call send_now) queues it for the automatic weekly digest every Monday 10am, which folds all pending drafts into one combined email instead of several separate sends. Actions: 'list' shows recent newsletters with status and segment; 'segments' returns live, throttle-aware recipient counts for each segment so you can preview reach before sending; 'pending_digest' lists drafts currently queued for next Monday's digest; 'create' drafts a newsletter (subject, content, segment); 'update' edits a draft/scheduled newsletter's fields; 'send_now' sends immediately in the background instead of waiting for the digest; 'destroy' deletes a newsletter.
  • admin_sponsors — ADMIN ONLY - manage site sponsors over MCP. Requires an admin Bearer token. Actions: 'list' shows sponsors with performance (impressions, clicks, CTR, running state); 'create' adds a manual sponsor (name, url, position, optional tagline/dates); 'update' changes fields on a sponsor by id; 'activate' / 'deactivate' toggle a sponsor; 'inquiries' lists sponsorship inquiries; 'inquiry_status' moves an inquiry through pending -> contacted -> converted/declined; 'orders' lists self-serve sponsor orders.
  • compare_stacks — Compare two technology stacks head-to-head with real adoption data. Returns products count, GitHub stars, collections, growth trends, and a winner. Uses the same scoring algorithm as the BuiltOnRails Stack Showdown feature.
  • detect_stacks — Detect technology stacks from a Gemfile, gemspec, package.json, or importmap.rb content. Paste your dependency file content and get back matched stacks with real adoption data. The killer feature for coding agents — understand your project's stack landscape instantly.
  • get_categories — Get all available stack categories with descriptions and stack counts. Useful for understanding what types of technologies are tracked and filtering searches.
  • get_collection — Get a curated stack collection by slug. Collections are hand-picked sets of technology stacks with notes and optional LLM prompts for AI context. Returns the collection with all stacks in order, notes, and the LLM prompt if available.
  • get_news — Read curated Rails ecosystem news and articles - the same pipeline behind builtonrails.com/daily. Returns recent items (title, url, summary, category, source). Filter by category (article, release, podcast, video, news), a specific date (YYYY-MM-DD), or a search term. Use this for 'what's new in Rails', release announcements, and article discovery.
  • get_product — Get detailed information about a specific production Rails application. Returns full product details including description, tags, member, stacks, and vote count.
  • get_products_using_stacks — Find real Rails applications that use specific technology stacks. Returns approved products using ALL specified stacks, with their full stack lists and vote counts. Great for finding real-world examples of specific tech stack combinations.
  • get_stack_recommendations — Get stack recommendations based on what real Rails apps use together. Given your current stacks, recommends the most popular stacks in a target category based on co-occurrence in production Rails applications. Available categories: Framework, Database, Frontend, Background, Search, Auth, Payments, DevOps, Testing, Analytics, LLM, AI/ML, Observability, Security, Email.
  • get_stack_trends — Get adoption trend data for a technology stack over time. Returns historical usage snapshots showing how many Rails apps use the stack, plus growth percentage. Useful for understanding if a stack is growing or declining.
  • my_product — OWNERS ONLY - manage your own products over MCP. Requires a write-scope Bearer token; you can only touch products you submitted or founded. Actions: 'list' shows your products; 'update' edits fields on one of your products (description, url, product_type, tags, github_repo_path); 'post_update' publishes a product update (title + update_type, optional content/url/version) shown on your product page; 'updates' lists a product's recent updates. Params: action (required); slug (required except for 'list').
  • search_products — Search real production Rails applications and the stacks they actually run. Returns approved products with name, URL, type, votes, and stacks. Filter by product type or sort by votes/newest.
  • search_stacks — Search for technology stacks (gems, frameworks, services) used by Rails applications. Returns matching stacks with real adoption data including product counts, GitHub stars, and category. Available categories: Framework, Database, Frontend, Background, Search, Auth, Payments, DevOps, Testing, Analytics, LLM, AI/ML, Observability, Security, Email.
  • submit_product — Add a Rails application to BuiltOnRails so its stack becomes part of the data. The product is created with 'pending' status and goes through admin approval. Attach stacks by name, or paste your Gemfile / package.json / importmap.rb content and the real stack is detected and attached automatically - the recommended path.

Data as of 2026-10-12T05:09:09+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections