MCP for Multi-platform

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 FastMCP (build servers) and mcp-inspector (debug): Smithery is distribution/hosting, not an SDK. Hosted registry is proprietary SaaS — supply-chain risk is real (past hosting incidents in the ecosystem). Prefer BYO HTTPS publish if you distrust hosted builds. Free discovery ≠ free infinite hosting.

Vs Composio (multi-app auth fabric): this is GitHub-only, official, and PAT/OAuth scoped to GitHub. Hosted remote path ties to GitHub/Copilot auth; local mode is yours to run. Permissions are the catch — over-scoped tokens are how agents leak. Not a generic toolkit marketplace.

Vs Composio and Smithery: treg is the self-hostable tool catalog and team-vault path, not a hosted connector marketplace or MCP registry alone. The Apache-2.0 license has additional terms — no competing hosted, managed, or embedded third-party service without prior written authorization — so it is not a clean “use the code anywhere” Apache grant. The curl|sh installer and credential injection deserve a disposable first run, pinned source, and narrowly scoped secrets.

Vs SuperGateway and mcp-remote: ContextForge is a heavier self-host governance/observability gateway, not a thin MCP bridge. Vs Smithery: this is a self-host gate you operate, not a hosted MCP marketplace. Open-issue count is high for the maturity pitch; local/JWT setups need real secrets — do not ship example tokens.

Vs Smithery: this is the protocol-org community registry, not a hosted freemium marketplace/CLI product. LICENSE is mid MIT→Apache-2.0 transition (Apache body + MIT-holdout preamble); GitHub SPDX often shows NOASSERTION — redistribution diligence required during the mixed-license era. Still in preview / API-freeze posture; pin expectations before building a business on the API shape.

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.

Vs Desktop Commander MCP: that is desktop-host terminal/files/processes; this is the chat-client→coding-agent hands layer (patches, interactive sessions, git) for any MCP client. Mid-★ (~1158) kept as Agents/MCP fill — Landlock is Linux-only; use Docker/VM for untrusted work.

Vs google-workspace-cli (`gws`): that is first-party Drive/Gmail/Calendar/Admin Workspace CLI+skills; this is NotebookLM/Gemini Notebook notebooks via MCP/CLI. Undocumented internal APIs that can change, plus cookie extraction from the browser for auth — personal/experimental risk, not a paid CLI wall. Enterprise Notebook host support is experimental.

★22,325 in about 99 weeks (~225 a week), with 1,284 open issues: judge it on the MCP/CLI substance, not the star count. Vs Neon / hosted DuckDB: those are managed engines; DBX is the agent-facing multi-engine client that sits on connections you already have. MCP is a separate install from the desktop binary; some engines still need the DBX agent/JRE path.

★2767 in about 24 weeks (~115 a week): judge it on the MCP/skills substance, not the star count. Vs GitHub MCP / Cloudflare Agents MCP / Composio: those are GitHub-native MCP, CF Workers agent/MCP surfaces, or freemium multi-app toolkits — this catch is AWS-first Agents/MCP + CLI proxy from the aws org. Empty AWS creds = no live APIs; treat account/IAM as the real gate, not the Apache license.

★8444 in about 79 weeks (~107 a week): judge it on the docs-MCP substance, not the star count. Vs github-mcp / context7 / mcp-remote: github-mcp is the official GitHub issues/PRs/code/workflows MCP; Context7 is library-docs retrieval; mcp-remote is a stdio↔OAuth remote shim — GitMCP’s catch is any-repo docs-as-MCP on gitmcp.io, not GitHub platform tools and not a transport proxy. Generic /docs mode must pick the right repo each turn; prefer pinned {owner}/{repo} URLs for security.

★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.

Every MCP server runs in its own container, so you need Docker or Podman even on a laptop. Identity and access policies only apply once you connect an OIDC/OAuth provider — out of the box it is isolation, not authorization. Stacklok sells an enterprise tier on top. Vs metamcp (aggregator/proxy that merges servers into one endpoint) and contextforge (gateway/federation): ToolHive’s lane is per-server container isolation plus a registry.

You write and maintain your SQL tools yourself in tools.yaml — the server does not invent safe queries for you. The prebuilt tool sets mostly target Google databases (AlloyDB, Cloud SQL, BigQuery, Spanner and friends); other engines get the generic tools. Renamed from genai-toolbox, so older guides use the old name.

It is a monorepo where each server is installed and configured separately, so wiring up several means several entries in your MCP config. AWS bills normally for whatever the tools do — an agent that creates resources creates real charges. Vs agent-toolkit-for-aws (plugins, skills and a single AWS CLI MCP proxy in one package): this is the catalogue of individual, service-specific servers.

Most servers need an Azure subscription or a sign-in to a Microsoft tenant before they do anything useful. Release tags are per package, so check which server a release belongs to.

Without an API key only scrape, search and parse work, and they are rate-limited; crawl, map and agent need a key and paid credits. Vs firecrawl (the scraping engine and API itself, AGPL-3.0): this is just the MIT MCP bridge to it.

Write access is on by default — add read_only=true unless you really want the agent changing your database, and scope it to a development project. Self-hosted Supabase needs extra setup compared with the hosted endpoint. Vs supabase (the platform itself): this is the agent interface to it.

For Atlas, the README points you to the MongoDB-hosted Atlas MCP server over OAuth instead; the local server is mainly for self-hosted MongoDB. Give it a read-only user unless the agent truly needs to write.

Tool calls act on your real Stripe account, so start in test mode with a restricted key. There are no GitHub releases — track the npm and PyPI packages instead. Vs stripe-cli (a terminal tool for developers to forward webhooks and inspect events): this is the toolkit an agent uses to call the Stripe API.

The hosted server works without a key but is rate-limited; higher limits and Exa Agent need an Exa API key or OAuth, and usage beyond that is paid. It searches and reads pages you point it at — for crawling whole sites, use a crawler such as Firecrawl. There are no GitHub releases.