Opendesignguard MCP

What opendesignguard-mcp MCP server does

The opendesignguard-mcp MCP server exposes a hosted agent design-system guard through MCP. Its tool set covers five related tasks: evaluating a design guard, describing detected gaps, creating a design receipt, proposing an agent-oriented fix, and exporting a design audit.

The service is intended for workflows that need structured review output rather than an informal design assessment. Receipts, audit logs, and reviewer-ready evidence are part of the documented service description. The repository itself is not the production implementation; it serves as public documentation and a directory-submission reference for the hosted product.

How it works

Requests are sent to the remote MCP endpoint at https://opendesignguard.clauxel.com/mcp. Clients communicate with that endpoint using Streamable HTTP and send JSON-RPC requests. Production calls must include an HTTP bearer token in the Authorization header:

Authorization: Bearer <token>

The token is issued through the product website after selecting a plan and creating or requesting access. A browser visit without authentication returns a JSON error rather than exposing internal service details.

Once connected and authenticated, an MCP client can invoke the five published tools. The available names are check_design_guard, explain_design_gap, issue_design_receipt, suggest_agent_fix, and export_design_audit.

Setup and configuration

Setup requires a paid hosted-service account or plan. Open the product website, choose a plan, and obtain an API token. Then configure an MCP client that supports remote Streamable HTTP servers with the published endpoint and bearer token. The supplied material does not define a local installation method, package, command-line launcher, or environment-variable configuration.

The public server card is available at https://opendesignguard.clauxel.com/server-card.json, and the registry identifier is com.clauxel.opendesignguard/opendesignguard-mcp. These links can help with client or directory configuration, but the README does not provide client-specific configuration examples.

Tools and capabilities

The opendesignguard-mcp MCP server publishes these capabilities:

• check_design_guard: run the documented design-guard check.
• explain_design_gap: explain a design gap identified by the guard workflow.
• issue_design_receipt: issue a structured design receipt.
• suggest_agent_fix: produce a suggested fix for an agent workflow.
• export_design_audit: export design-audit information for review or recordkeeping.

The README names the tools but does not document their individual input schemas, output fields, validation rules, or billing behavior. Those details should be confirmed through the service or its server card before implementation.

Limitations and notes

This is a paid remote MCP service, not a self-hosted server described by the repository. Production use depends on obtaining a bearer token and on using an MCP client with Streamable HTTP support. The available material does not establish offline operation, local deployment, specific client compatibility, or a particular software license. It also does not describe the design-system formats or source-control systems accepted by the tools.

Choose this service when remote design-system checks and structured audit evidence are the requirement. For a local, unauthenticated, or fully documented tool implementation, the repository excerpt does not provide enough information to confirm that fit.