Tool-calling runtime that holds user OAuth tokens and exposes a catalogue the vendor puts at 7,500+ tools over 81 MCP servers, metered per call.
Teams building agents that act as a specific end user rather than as a service account, where the hard part is authorization rather than the API call. Arcade states it manages OAuth flows, stores user tokens, API keys and secrets, and applies per-action authorization at runtime, with user identity sourced from Auth0, Clerk, Microsoft Entra ID, Okta or Stytch. It also fits organisations consolidating MCP sprawl: the docs describe MCP Gateways, a private registry, bring-your-own-MCP-server registration, OpenTelemetry audit logs, rate limiting and group-based tool access.
Volume workloads will feel the meter: Team bills $0.10 per auth event and $0.01 per tool call on top of a $25/month platform fee, with no published volume discount outside a quote-only Enterprise tier whose bundle sizes are not stated. Anyone who needs to self-host should check the plan boundary first, because the pricing page puts self-hosting, VPC and air-gapped deployment under Enterprise only and says Free and Team are fully managed on Arcade Cloud; the MIT-licensed arcade-mcp Python framework lets you build and run your own servers, but that is not the same as running the managed runtime. SSO, RBAC, audit logs and private registry access are also Enterprise-only, and GCP deployment is marked coming soon.
Pros
Cons
On the Team plan it is $0.01 per tool call plus $0.10 per auth event, on top of a $25/month platform fee, and Arcade states pricing is not per seat. The Free plan includes 2,000 auth events and 2,000 tool calls a month at $0. Enterprise replaces per-unit rates with annual bundles and discounted overage, but the bundle sizes are quote-only and not published.
Authorization is the product. Arcade manages the OAuth flows and stores user tokens, API keys and secrets for connected services, applying per-action authorization at runtime and distinguishing server-level from tool-level authorization. User identity can come from Auth0, Clerk, Microsoft Entra ID, Okta or Stytch. In the open-source arcade-mcp framework, tools declare scopes via requires_auth and the README states the client and LLM never see secret values.
Only on Enterprise. The pricing page lists deployment on Arcade Cloud, in your VPC, or fully air-gapped under Enterprise, and says Free and Team are fully managed on Arcade Cloud. The docs also list self-host with Helm, Azure and AWS Marketplace, Arcade Worker and hybrid MCP servers as options, with GCP coming soon. Separately, the MIT-licensed arcade-mcp Python framework can be run anywhere you like.
Yes — arcade-mcp, the Python framework for building MCP servers and tools, is MIT-licensed on GitHub. It installs via uv tool install arcade-mcp, exposes the arcade_mcp_server module, supports stdio (default) and HTTP+SSE transports, and can protect production HTTP endpoints with OAuth 2.1 Bearer resource-server auth. The managed runtime, tool catalogue and governance layer are a closed hosted service priced separately.
Facts sourced from the vendor’s own site, last verified 2026-10-10.
The Weekly Source
One email a week. New listings, repriced tools, and the ones we would skip - including this one if its pricing changes.
