01 · ABOUT

What Arcade.dev does

Arcade is a runtime that sits between AI agents and the systems they act on: it hosts MCP servers and tools, handles the OAuth handshake and token refresh with each upstream API so that neither the MCP client nor the LLM sees the token, and enforces per-action authorization against the organisation's own identity provider. It ships a catalog of 7,500+ prebuilt tools across 81 MCP servers, an open-source Python framework and CLI (arcade-mcp) for building and deploying your own, and MCP gateways that federate tools from several MCP servers into a single URL for the agents and apps that consume them.

Why teams reach for it: Arcade takes user-level authorization out of the agent and makes it the runtime's job: a tool declares the OAuth scopes it needs, Arcade prompts the end user, stores and refreshes the token, and injects it per call so the MCP client and the LLM never see it, while every action is authorized at runtime against the organisation's existing identity provider at the intersection of what the agent and that user may each do.

HybridOpen SourcePythonTypeScriptMCP Server & Client
02 · TECHNICAL SPECIFICATIONS

How Arcade.dev compares

Fields the vendor doesn't document are left blank here rather than guessed — a blank means nothing verified, not a "no."

Credential Storage Location
Either
03 · NEW TO MCP?
How will tools receive safe access to external systems?

Credentials & connections tools manage how an MCP server safely accesses external systems, like databases or APIs, on a user's behalf.