From trial to team rollout
The agent plugin serves one person evaluating Arcade. It points every install at a shared Arcade gateway, offers a broad selection, and identifies you by the apps you signed in to yourself. That is exactly what you want while you are finding out whether a workflow is worth having.
Once a team depends on that workflow, three things change. This page names them and points at the setup for each.
If your loaded the plugin’s skills, ask it to run /scale-arcade. The
skill walks through the same decisions interactively against your own
workspace.
You want your own gateway
An MCP Gateway is the endpoint your team’s clients connect to, and it is where you decide what those clients can do. Create one per in the Arcade dashboard so each project gets a URL you control, its own list, and its own audit trail.
Clients connect to it exactly the way they connected to the plugin’s gateway. See the MCP client guides for Cursor, Claude Code, Claude Desktop, VS Code, and Copilot.
You want a curated tool list
The gateway is the filter that decides which tools reach your . Open the Allowed picker on your gateway and select across everything in scope: Arcade-hosted toolkits from the integrations catalog, remote MCP servers you register, and your own custom MCP servers deployed with Arcade Deploy.
A smaller, deliberate tool list makes more accurate, not less capable. Save the gateway and connected clients see the new list on their next request, with no restart.
Beyond the allowlist, contextual access lets you allow or deny each individual call as it arrives, and audit logs and tool executions show you what actually ran.
You want your own user identities
During a trial, you are the only user, and browser sign-in is enough. In production, each of your end users needs their own authorization, so an acting for one person can never reach another person’s data.
Configure a User Source on your gateway and Arcade redirects each end to your existing identity provider, whether that is Entra ID, Okta, Auth0, Clerk, or another OIDC provider, then identifies them by an OIDC subject claim.
Going beyond MCP
Connecting a client to a gateway takes the least work, and for many teams it is the whole rollout. When you are building your own product rather than configuring an , call Arcade directly instead:
- Arcade API reference: the REST surface for calling and authorization
- Agent frameworks for LangChain, CrewAI, OpenAI , Google ADK, Mastra, Vercel AI SDK, and more
- Get an API key: required once you are calling Arcade from your own code
- Build user-facing agents: patterns for handling authorization on behalf of your