In-depth architectural comparison of the Delego and Platform 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.
At a Glance & Executive Verdict
Delego
Security · Local stdio
Quality: 41/100 (Fair) | Auth: other
Platform
Security · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Delego if you need specialized Security tools running via a local process. Choose Platform if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Delego when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: Intent/fingerprint binding against the open Delego wire specification (protocol 0.3), Policy-based action authorization independent of credential scope, Human-in-the-loop CLI approval for flagged actions.
Intent-bound action authorization for AI agents: policy, human approval, and a signed audit trail.
Governance proxy for MCP servers. Wraps any upstream server with policy evaluation, human approval workflows, and hash-chain audit trails. 18+ framework integrations. Apache 2.0 SDK.
Delego is categorized under Security and uses a local stdio subprocess. In contrast, Platform belongs to Security using local stdio subprocess. Select Delego when you need capabilities focused on security and Platform when you require tools for security.