Gatekeeper vs Opendesignguard MCP
A side-by-side look at the Gatekeeper and Opendesignguard MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gatekeeper for security work as a local process; choose Opendesignguard MCP for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gatekeeper when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose Opendesignguard MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_design_guard, explain_design_gap, issue_design_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 43/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Gatekeeper | View Opendesignguard MCP |
Tools & capabilities
Gatekeeper tools
No tool names declared yet. Check the project README from the listing page.
Opendesignguard MCP tools 5
check_design_guardexplain_design_gapissue_design_receiptsuggest_agent_fixexport_design_audit
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.
Gatekeeper
{
"mcpServers": {
"gatekeeper": {
"command": "npx",
"args": [
"-y",
"@runestone-labs/gatekeeper-mcp"
]
}
}
}
Opendesignguard MCP
{
"mcpServers": {
"opendesignguard-mcp": {
"url": "https://opendesignguard.clauxel.com/mcp"
}
}
}
Frequently asked questions
Gatekeeper is categorized under Security and uses a local stdio subprocess. Opendesignguard MCP belongs to Security and uses a remote HTTP/SSE transport. Pick Gatekeeper for security work and Opendesignguard MCP for security.
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.
Gatekeeper has no declared pricing — check the project's own site. Opendesignguard MCP has no declared pricing — check the project's own site. 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 gatekeeper and opendesignguard-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gatekeeper has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Opendesignguard MCP has 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.