A side-by-side look at the Policy Gate and Delego MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Policy Gate for security work; choose Delego for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Policy Gate when
You need dedicated capabilities in the Security domain.
No tool names declared yet. Check the project README from the listing page.
Delego 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.
Policy Gate
No confirmed install command for Policy Gate yet — follow the setup steps linked from its listing page rather than a guessed package name.
Policy Gate is categorized under Security and uses an install path we have not confirmed yet. Delego belongs to Security and uses a local stdio subprocess. Pick Policy Gate for security work and Delego 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. Policy Gate has no confirmed install command yet — follow its own setup instructions.
Policy Gate has no declared pricing — check the project's own site. Delego 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 policy-gate and delego as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Policy Gate has a quality signal of 32/100 (Emerging) with 1 views, 0 installs and 1 GitHub stars. Delego has 41/100 (Fair) with 2 views, 0 installs and 25 GitHub stars.