MCP for Node.js

Plumbing only — not a Playwright/Chrome DevTools MCP capability server. It does not add browser, docs, or symbol tools; it only rewires transport. If your client already speaks the server’s native transport, you do not need it.

Vs SuperGateway (bidirectional stdio↔SSE/WS bridge): mcp-remote is the client-side remote+OAuth drop-in, not a capability server and not a full gateway product. Some clients already speak unauth remote MCP — you only need this for OAuth/legacy stdio hosts. Adds a local Node process in the path.

Debug surface, not a production MCP gateway or registry (see Smithery) and not transport glue (SuperGateway/mcp-remote). You still author servers elsewhere (FastMCP, etc.). v2 is the active line; pin versions in CI.

Vs FastMCP (Python MCP framework), mcp-agent (MCP-as-runtime + Temporal), and Composio (managed tool/auth catalog): mcp-use is fullstack MCP app/server kit, not a multi-SaaS OAuth fabric. Manufact Free is an optional hosted/upsell path — core stays MIT you run yourself.

Vs mcp2cli (runtime MCP/OpenAPI→CLI, zero codegen): mcporter leans generate-cli/emit-ts packaging and TS API shape — pick based on whether you want codegen’d CLIs vs pure runtime discovery. You still trust the MCP servers you wrap. Not an MCP transport gateway (see SuperGateway/mcp-remote).

Vs Playwright MCP / Invisible Playwright MCP: those are desktop browser MCP; this is native mobile a11y-tree MCP. Vs ARTEMIS: Google Android NL+MCP automation — Mobile MCP is iOS+Android a11y MCP without the Android-only NL agent framing. Optional Mobile Next Cloud freemium is a separate hosted lane.

Vs MCP Registry: listing/discovery, not an aggregator runtime. Vs ContextForge: protocol gateway + A2A/OTel plane. Vs Klavis: freemium integrations/Strata. Vs Smithery: hosted marketplace. Vs SuperGateway: transport stdio↔SSE only. Soft maintainer capacity thin — last push 2026-06-22; default branch is `ai-dev` (caution); author says core still works / will keep merging PRs — shippable with eyes open.

★15941 in about 85 weeks (~187 a week): judge it on the Figma→agent MCP loop, not the star count. Vs Figma (design tool) / playwright-mcp / chrome-devtools-mcp: Figma is the collaborative canvas; Playwright/DevTools are browser automation — this catch is Figma file context into the coding agent via MCP. Needs a Figma API key; design-file access and rate limits are the real gate, not the MIT license.

Vs mobile-mcp / chrome-devtools-mcp / playwright-mcp: mobile-mcp is Apache native iOS+Android a11y-tree control (sim/emu/real); DevTools/Playwright are browser — Mobile Build MCP’s catch is build/compile tooling for Apple projects, not UI automation. macOS + Xcode required; Android is out of scope; ★6448 is healthy but still early — pin a release before fleet install.

Actor runs and Apify platform usage are billed — the MCP server is MIT, the data path is freemium/paid compute. Vs playwright-mcp / browser-use / firecrawl-class scrapers: those drive browsers or crawl APIs you own — Apify MCP’s catch is Store Actors as MCP tools. Legacy `/sse` endpoint removed — point clients at https://mcp.apify.com; pin which Actors agents may call.

Native depth is only as good as the engine behind it: Hopper is commercial (demo mode otherwise), IDA is commercial, Ghidra is free but heavy, and Windows Ghidra support is marked experimental. Needs Node.js 22.19+; APK and firmware paths want JADX/JDK or Binwalk/Unblob on Linux or macOS. The pitch is “see a feature you like, build a version” — many app licenses forbid reverse engineering, and the project itself says you are responsible for authorization and the law. Releases move fast; keep it updated.