Back to Gap Map Product / UX / Agent tools & connectors

Arcade.dev

Arcade
closed / Overall score: 3.2

Runtime that lets agents act in their users' accounts: it runs the OAuth flow for each end user, keeps the tokens in an encrypted vault, renews them, and injects them into tool calls so neither the client nor the model sees them. It serves a catalog of prebuilt MCP servers for business systems through scoped MCP gateways, with access rules and audit logs, and its open-source framework, arcade-mcp, builds custom servers that run standalone or deploy onto the platform. The platform runs as Arcade Cloud or is installed into a customer's own cluster.

Scored as the hosted Arcade platform, not as the arcade-mcp framework (R-2026-11-12-i). The platform's Engine, token vault and gateways are not published, so it is closed, matching Composio, whose MIT SDKs are likewise clients of a closed hosted service. arcade-mcp is a real MIT framework that runs MCP servers without the platform; it would be assessed as its own product rather than raising this one. The declared artifacts are the framework's, and adoption is read from its downloads, as Composio's is read from its SDK.

Openness

1 medium confidence
1.0
license
Proprietary (the Arcade platform's code is not published)
source
closed (the Engine, which runs the OAuth flows, holds the token vault and serves MCP gateways, ships with the rest of the platform only as Arcade Cloud or as Arcade's container images and Helm chart; no repository publishes it)
framework
MIT (ArcadeAI/arcade-mcp, a separate open framework for building and running MCP servers; it is not the platform's source)
backend
commercial (Arcade Cloud, with deployment in a customer's VPC or air-gapped listed under the Enterprise plan)

Arcade's platform, the Engine that runs the OAuth flows, stores each user's tokens and serves the MCP gateways, is not published: it runs as Arcade Cloud or is installed from Arcade's own images under an Enterprise plan. Arcade does publish arcade-mcp, an MIT-licensed framework for building MCP servers that also run on their own, but that framework is a separate open project and not the source of the platform scored here.

  • https://docs.arcade.dev/en/operate/deploy/architecture recorded 2026-11-12

    The platform architecture page lists the Engine ("Tool execution and routing, the token vault, and MCP gateways"), Coordinator, Experience API, Dashboard, OpenFGA and Usage services as what a self-hosted deployment runs.

  • https://docs.arcade.dev/en/operate/deploy/helm recorded 2026-11-12

    The self-hosting page says "The Arcade Helm chart deploys the full Arcade platform onto a Kubernetes cluster you manage" and installs it with "helm install arcade oci://public.ecr.aws/s5i6x9d1/charts/arcade"; no source repository for the platform is named.

  • https://raw.githubusercontent.com/ArcadeAI/arcade-mcp/main/LICENSE recorded 2026-11-12

    The LICENSE is the MIT License text, headed "Copyright (c) 2025, Arcade AI".

  • https://raw.githubusercontent.com/ArcadeAI/arcade-mcp/main/README.md recorded 2026-11-12

    The README calls arcade-mcp the "Open-source Python framework for building MCP servers and tools" that "powers the 7,500+ prebuilt tools across 81 MCP servers at Arcade.dev". Through Arcade Cloud "the Arcade Engine fulfills authorized tool calling flows"; run standalone, you "Supply your own access tokens for tools with requires_auth".

  • https://www.arcade.dev/pricing recorded 2026-11-12

    The pricing page offers Free, Team and Enterprise plans; Enterprise lists "Flexible deployment options on Arcade Cloud, in your VPC, or fully air-gapped".

Adoption

2 medium confidence
2.0

Adoption is the trailing month of PyPI downloads of arcade-mcp, the CLI and framework developers install to build servers and deploy them to Arcade. Agents that only call Arcade's hosted tools through its API clients never install it, so the figure counts tool builders rather than the platform's users.

Capability

5 medium confidence
5.0

Arcade reaches many systems, runs the OAuth flow and keeps each user's tokens itself, and hosts the tools it calls, which puts it level with Composio. What distinguishes it from a plain MCP server is that the caller never handles a token.

  • https://docs.arcade.dev/en/get-started/about-arcade recorded 2026-11-12

    The About page: "Arcade handles OAuth and manages user tokens, API keys, and secrets", with "7,500+ agent-optimized tools across 81 MCP servers", and a central control plane with a shared registry and audit logs.

  • https://docs.arcade.dev/en/operate/deploy/architecture recorded 2026-11-12

    The Engine "Runs the token vault: it takes each end user through the OAuth flow for a provider such as Google or Slack, stores the resulting token encrypted, renews it when a tool call finds it expired, and supplies it to the tool at execution time", and "Serves MCP gateways".

Verified 2026-11-12