Side-by-Side Model Context Protocol Comparison
Proximo vs Kubernetes MCP Server
In-depth architectural comparison of the Proximo and Kubernetes MCP Server 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
Proximo
Cloud Platforms · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Kubernetes MCP Server
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: other
Verdict Summary: Choose Proximo if you need specialized Cloud Platforms tools running via a local process. Choose Kubernetes MCP Server if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Proximo when:
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Free / Open Source).
- You have access to required keys:
PROXIMO_API_BASE_URL, PROXIMO_NODE, PROXIMO_TOKEN_PATH. - Primary tools included: audit_entries, audit_verify, proximo_call.
Choose Kubernetes MCP Server when:
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: other (Free / Open Source).
- Primary tools included: configuration_contexts_list, targets_list, configuration_view.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Proximo Tools (7)
audit_entries
READ-ONLY: WHO changed WHAT and WHEN — guest configuration changes and every other
audited action, read back from the PROVE ledger.
Newest first. This is how you answer "who changed this guest" or "what has this caller
done". `matched` counts entries passing your filters, `total` counts the whole ledger,
and `truncated` says so when `limit` cut rows. An entry with no principal returns null
plus a note: the ledger not capturing an identity is a fact about the log, never a claim
that nobody was responsible. This READS the chain; `audit_verify` PROVES it is intact.
audit_verify
Verify the tamper-evident audit ledger's hash chain — PROVE the log is intact.
Pass `expected_head` (the head() value you pinned off-box) to also catch tail
truncation, a forged tail-append, or a full file replacement — a forward walk
alone can't see those. Falls back to PROXIMO_AUDIT_EXPECTED_HEAD when omitted.
proximo_call
Call any Proximo tool by exact name, including ones not in this server's listed tools.
Get the argument shape from proximo_tool_schema first. Same gates as calling it directly:
dry-run PLAN, ledger entry, token ACL. A smaller doorway, not a looser one.
proximo_recall
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).
Proximo Configuration
Kubernetes MCP Server Configuration