In-depth architectural comparison of the Mcp Server Docker and Sugra API 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
Mcp Server Docker
Cloud Platforms · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Sugra API
Cloud Platforms · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Server Docker if you need specialized Cloud Platforms tools running via a local process. Choose Sugra API 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 Mcp Server Docker when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: DOCKER_HOST.
Primary tools included: Natural language container composition with plan and apply loop, Container lifecycle management: create, run, start, stop, remove, Image management: list, pull, push, build, remove.
Mcp Server Docker is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Sugra API belongs to Cloud Platforms using local stdio subprocess. Select Mcp Server Docker when you need capabilities focused on cloud platforms and Sugra API when you require tools for cloud platforms.
One-step: find best endpoint for a natural-language query and call it. Combines search + call in one round trip.
search_endpoints
Search the bundled endpoint catalog. Runtime search does not fetch `/openapi.json`.
describe_endpoint
Inspect an endpoint by `operation_id`, including path, method, parameters, required inputs, `agent_hints`, and `request_body_schema` for JSON-body POST operations.
call_endpoint
Call a Sugra API operation by `operation_id`. Arbitrary path calls are no longer supported.
list_toolsets
List catalog groups with endpoint counts and descriptions.
list_sources
Show bundled catalog source metadata.
sugra_entity_screen
Screen a name against sanctions and watchlists (Sugra Entity).
sugra_entity_lookup
Composed entity lookup by identifier - `anchor` is `lei` or `vat`, plus the identifier `value`; returns registry identity + screening (Sugra Entity).
resolve_entity
Free text (ticker, company, indicator, coin, currency pair) to a canonical market or macro entity. Ambiguous matches return ranked candidates, never a silent pick.
get_snapshot
Entity plus a named recipe to one composed current view with freshness, provenance, coverage, and billing blocks. Composed calls charge a fixed recipe cost (1-2 requests) from the daily quota.
get_timeseries
Entity plus metric (`price`, `macro_series`, `etf_flows`) to a bounded series with an explicit downsampling flag.