Crystallize MCP vs MCP Accessibility Scanner

In-depth architectural comparison of the Crystallize MCP and MCP Accessibility Scanner MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Crystallize MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: browse_catalogue, get_item, search_catalogue.

Explore Crystallize MCP Details

Choose MCP Accessibility Scanner when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: scan_page, audit_site, scan_page_matrix.

Explore MCP Accessibility Scanner Details

Feature & Specification Comparison

Specification	Crystallize MCP Browser Automation	MCP Accessibility Scanner Browser Automation
Summary	Crystallize headless commerce tools for AI agents via Model Context Protocol	MCP server for automated web accessibility scanning with Playwright and Axe-core.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "crystallize-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hayodev/crystallize-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-accessibility-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-accessibility-scanner"
      ]
    }
  }
}

Related MCP Server Comparisons