Melta UI vs Texas Ag Opinions

A side-by-side look at the Melta UI and Texas Ag Opinions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Melta UI logoMelta UILegal · Local subprocess (stdio)AI-Ready design system MCP: melta UI tokens, component contracts, 99 rules, check_html self-verify68GreatAuth: not declaredTexas Ag Opinions logoTexas Ag OpinionsLegal · Local subprocess (stdio)Texas Attorney General opinions — statute-citation search over recorded45FairAuth: no auth required

Verdict: choose Melta UI for legal work as a local process; choose Texas Ag Opinions for legal as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Melta UI logoChoose Melta UI when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_token, get_component, check_rule.
Explore Melta UI

Texas Ag Opinions logoChoose Texas Ag Opinions when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Texas Ag Opinions

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMelta UI logoMelta UITexas Ag Opinions logoTexas Ag Opinions
CategoryLegalLegal
Quality signal68/100 · Great45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2020
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

Melta UI tools 6

  • get_tokenGet a design token by dot-path. Returns the token object with its value and class mapping.
  • get_componentGet component metadata including variants, sizes, accessibility requirements, HTML sample, per-state specs (stateSpecs: disabled/loading/open/empty etc. — each with delta class strings + aria changes), and anatomy parts (overlay/container/th etc. with element/roles/class). Prefer these structured fields over inferring states from the HTML sample.
  • check_ruleCheck class strings against this design system's prohibition rules. Returns violations with reasons and alternatives.
  • check_htmlLint a full HTML/JSX source against melta-ui rules — the same checks as CI and the PostToolUse hook (class rules + html-attr rules + composition rules for HTML). Use this AFTER generating UI code to self-verify before presenting it. Response always includes coverage info (manual rules cannot be auto-checked).
  • searchSearch across tokens and components by keyword. Matches against names, values, class strings, and descriptions. Returns up to 20 results (truncated flag when more matched).
  • get_rulesGet melta-ui prohibition rules from rules.json (107 total). Use this to retrieve manual/contextual rules that check_rule cannot auto-detect. Supports filtering by category, severity, or detector.

Texas Ag Opinions 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.

Melta UI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "melta-ui": {
      "command": "npx",
      "args": [
        "-y",
        "melta-ds-mcp"
      ]
    }
  }
}

Texas Ag Opinions

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "texas-ag-opinions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-texas-ag-opinions"
      ]
    }
  }
}

Frequently asked questions

Melta UI is categorized under Legal and uses a local stdio subprocess. Texas Ag Opinions belongs to Legal and uses a local stdio subprocess. Pick Melta UI for legal work and Texas Ag Opinions for legal.

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.

Melta UI has no declared pricing — check the project's own site. Texas Ag Opinions 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 melta-ui and texas-ag-opinions as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Melta UI has a quality signal of 68/100 (Great) with 3 views, 0 installs and 202 GitHub stars. Texas Ag Opinions has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.