Dev Changes vs Roast My Design System

A side-by-side look at the Dev Changes and Roast My Design System MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

D
Dev ChangesVersion Control · Remote HTTP/SSE
Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.43FairAuth: oauth 2.0
Roast My Design System logoRoast My Design SystemDeveloper Tools · Local subprocess (stdio)Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.51GoodAuth: no auth required

Verdict: choose Dev Changes for version control work over a hosted endpoint; choose Roast My Design System for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

D
Choose Dev Changes when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Dev Changes

Roast My Design System logoChoose Roast My Design System when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Roast My Design System

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
D
Dev Changes
Roast My Design System logoRoast My Design System
CategoryVersion ControlDeveloper Tools
Quality signal43/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0No auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—27
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Dev Changes tools

No tool names declared yet. Check the project README from the listing page.

Roast My Design System tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dev Changes

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dev-changes": {
      "url": "https://openhelm.ai/mcp/dev-changes"
    }
  }
}

Roast My Design System

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "roast-my-design-system-2": {
      "command": "npx",
      "args": [
        "-y",
        "roast-my-design-system@latest"
      ]
    }
  }
}

Frequently asked questions

Dev Changes is categorized under Version Control and uses a remote HTTP/SSE transport. Roast My Design System belongs to Developer Tools and uses a local stdio subprocess. Pick Dev Changes for version control work and Roast My Design System for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Dev Changes has no declared pricing — check the project's own site. Auth: oauth 2.0. Roast My Design System is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dev-changes and roast-my-design-system-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dev Changes has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Roast My Design System has 51/100 (Good) with 5 views, 0 installs and 27 GitHub stars.