MCP.so
Sign In

Rams MCP ServerVerifiedFeatured

@HSLA0001 Inc.

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Last updated

Category

Developer Tools

Author

HSLA0001 Inc.

Submitted by

Eli Rousso

About Rams MCP Server

Design review for UI code, inside your agent. quick_review checks the files you just changed in about ten seconds. review_files returns a 0-100 score and patches. verify_fixes confirms the fixes landed, free. review_url reviews a live page by its address. 348 rules across accessibility, color, typography, spacing, components, UX, motion, craft and native SwiftUI (live list at rams.ai/rules). Connect at https://worker.rams.ai/mcp and approve access in the browser; free plan: 15 reviews to try it, no card.

Connection details

https://worker.rams.ai/mcp

Setup

claude mcp add rams --transport http https://worker.rams.ai/mcp

Rams MCP Server tools

5

Check how many Rams reviews this account has used and how many are left. Free to call. It does not use a review.

Full Rams design review of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns a 0-100 score (criticals cap it: one caps at 59, two at 49, three or more at 39), issues with severity, category, file:line, and concrete fixes as patches. Call it once at the end: before a commit, or when the user wants a score or a final check. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx). Each call uses one review credit. Reviewing a few files needs no permission. Ask the user before a whole-codebase audit (dozens of files), since it spends their allowance. For quick feedback while you work, use quick_review.

Fast design and accessibility check of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns the top issues with severity, category and file:line in about 10 seconds. Call it when the user pastes or uploads UI code, asks whether a design is good or accessible, or when you just wrote or changed a component, page or view. You do not need to ask first. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx, pasted/index.html) and the full code. Five quick checks cost one review credit (two on the free plan). It reads code only, not screenshots or URLs. It returns no score and no patch: fix the issues yourself. For a score or patches, use review_files.

Re-check findings from an earlier Rams review against the updated code. Pass the new version of each file under the same path as before, plus the findings. Returns fixed or still present for each one. Free: it never counts against the user's quota. Use it after you fix the issues.

Review a live public web page by its URL, no code needed. Rams opens the page at desktop (1440px) and phone (390px) widths, measures the rendered page and looks at both screenshots, then returns the top design issues (severity, category, where on the page, and a fix in plain words) with a 0-100 score. Use it when the user names a site or a page: "review rams.ai with Rams", "how does my landing page look?". It takes up to a minute and uses one review credit. Public pages only: no sign-in pages, localhost or private addresses. It returns no code patches. If the user has the code for the page, use quick_review or review_files on those files instead.

Overview

What is Rams?

Rams reviews UI code for design quality, the things linters can't see: weak hierarchy, hardcoded colors that bypass a design system, missing interaction states, motion without a reduced-motion guard, controls a keyboard or screen reader can't use.

Your agent writes the code. Rams reviews it before it's committed.

The tools

  • quick_review: checks the files you just changed in about ten seconds. Use it like a type check, after each component.
  • review_files: up to 20 files in, a 0-100 design score out, with issues by severity, category and file:line and a patch for each fix.
  • verify_fixes: send the changed code back and Rams confirms the fixes landed. Free.
  • review_url: reviews a live public page by its address, at desktop and phone widths.
  • usage: how many reviews are left. Free.

What it checks

348 versioned rules across 9 categories: accessibility (WCAG 2.2 AA), color, typography, spacing, components, UX, motion, craft and native (SwiftUI and Apple HIG). The live list is at rams.ai/rules.

Works with React, Vue, Svelte, Angular, React Native, SwiftUI and HTML/CSS.

Setup

  1. Add the server (config above). Clients that support OAuth open the browser to approve access, no key needed. Otherwise send Authorization: Bearer rams_YOUR_API_KEY from rams.ai/app/settings.
  2. The free plan includes 15 reviews to try it, no card.
  3. Ask your agent for a design review before committing UI changes.

A standing instruction for AGENTS.md or CLAUDE.md:

After changing UI code, run a Rams quick_review. Before committing, run review_files and fix any critical issues.

Same engine, more places

The same engine reviews every pull request through the GitHub App and scores public repos at rams.ai/scores. See a real review before you install anything: rams.ai/score/antiwork/gumroad

Frequently asked questions

1

What is the Rams remote MCP server?

The Rams remote MCP server is a hosted Model Context Protocol endpoint at https://worker.rams.ai/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Rams MCP server?

Add the endpoint https://worker.rams.ai/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Rams MCP server require authentication?

Yes. Rams uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Rams MCP server use?

Rams exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments