In-depth architectural comparison of the Gws Admin MCP and Emilia Protocol 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
Gws Admin MCP
Security · Local stdio
Quality: 36/100 (Fair) | Auth: OAuth 2.0
Emilia Protocol
Security · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Verdict Summary: Choose Gws Admin MCP if you need specialized Security tools running via a local process. Choose Emilia Protocol 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 Gws Admin MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_SA_KEY, DELEGATED_ADMIN, CUSTOMER_ID, GWS_ADMIN_CONFIG_DIR, GWS_ADMIN_ALLOW_WRITE, GWS_ADMIN_AUDIT.
Primary tools included: Read-only mode with 17 default tools, Google Workspace Admin SDK and Groups Settings access, Domain-wide delegation through a service account.
Safe Google Workspace admin for AI agents: read-only by default, confirm-gated deletes, audit log.
Human sign-off + trust receipts for AI agents: requires a named human's approval before an irreversible action (payment release, record change, deploy), then mints an offline-verifiable Ed25519 Trust Receipt. Also exposes trust profiles, receipt verification, disputes, and delegation. Apache-2.0; policy engine formally verified. Install: npx -y @emilia-protocol/mcp-server.
Category & Scope
Tools & Capabilities Breakdown
Gws Admin MCP Tools (6)
Read-only mode with 17 default tools
Google Workspace Admin SDK and Groups Settings access
Domain-wide delegation through a service account
Confirmation gates for destructive actions
Local JSONL audit logging with secret redaction
Automatic pagination for list operations
Emilia Protocol Tools (3)
ep_guard_action
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gws Admin MCP is categorized under Security and uses a local stdio subprocess. In contrast, Emilia Protocol belongs to Security using local stdio subprocess. Select Gws Admin MCP when you need capabilities focused on security and Emilia Protocol when you require tools for security.
Request authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
ep_check_signoff
Poll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.
ep_verify_receipt
Ask the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.