Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Code-mode MCP server: collapses N user-defined tools into a two-tool surface (executecode + docssearch). Backed by a unified capability manifest (allowedHosts / cpuMs / memoryLimitBytes) honoured across three sandbox kernels — in-process node:vm, WASM (QuickJS / Pyodide / Wasmtime), and remote microVM (E2B / Cloudflare Sandbox). Token-saving benchmark in repo CI.
Self-hostable GPU-aware job broker for your own machines. The MCP server exposes the queue as nine tools (submit, status, logs, list, cancel, preempt, workers, job-get, worker-delete) so an agent can dispatch long-running or GPU jobs that outlive the session, route them by VRAM tier, and babysit them across sessions. pip install "jobd[mcp]".