Skip to Content
Get StartedAgent PluginFrom personal use to team rollout

From personal use to team rollout

The agent plugin serves one person working on their own. Every install points at the same global gateway URL. Arcade uses the app connections authorized for your signed-in identity. Authorize only the you intend the to use.

What the plugin gives you is a broad selection and an identity that is yours alone, which is what you want for your own work.

Once a team depends on that workflow, three questions you never had to answer start to matter:

  1. Where does your team connect?
  2. Which can they call?
  3. Who is each end ?

Each one has a section below, in that order.

If your client loads the plugin’s skills, ask Arcade to help move your workflow onto a team gateway. In Codex, use $arcade:scale-arcade.

Where does your team connect?

An MCP Gateway is the endpoint your team’s clients connect to, and it is where you decide what those clients can do. Create a gateway in the relevant Arcade for the workflow and boundary you need from the Arcade dashboard .

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.

Which tools can they call?

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.

Who is each end user?

When you are the only user, signing in to each app yourself 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.

Choose how your end users sign in. Internal teams whose users are Arcade members can use Arcade Auth. If already have identities in your organization’s OIDC provider, configure a User Source on the gateway.

Building your own product?

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:

Last updated on
Any MCP clientGet an API key