Install the Arcade agent plugin
This guide is for agent developers installing Arcade in their own coding agent or desktop client. Personal installs use Arcade’s hosted gateway without creating or configuring a gateway.
Outcomes
Install the Arcade plugin in a supported client and connect to its hosted gateway.
Prerequisites
- A supported client: Cursor, Claude Code, VS Code, GitHub Copilot CLI, Codex, or Claude Desktop
- An Arcade
- For Claude Code, Claude Cowork, Cursor CLI, and GitHub Copilot CLI: Node.js on the PATH of the host that launches their routing hooks. Those hooks run
node. Cursor IDE and Cloud , VS Code, Codex, and Claude Desktop Chat do not need Node.js.
Install
The cross-client npx plugins add command does not finish every client
install. Use the client-native steps below so the gateway and every supported
plugin component load together. The install commands below use the plugin
repository and are not pinned to a release.
Claude Code
-
Add the Arcade marketplace and install the plugin:
Terminalclaude plugin marketplace add ArcadeAI/arcade-plugin claude plugin install arcade@arcade -
Run
/reload-pluginsif Claude Code is already open. -
Verify the install with
claude plugin listor/plugin.
Sign in
Arcade separates gateway sign-in from app authorization:
- Into the gateway. Your client asks you to sign in when it first connects. Sign in to Arcade in the browser so your client can connect to the gateway.
- Into each app. When a task needs an app, your gives you a browser sign-in link for the required permissions. After approval, Arcade stores the authorization. You may need to reconnect if the connection expires or a later task needs additional permissions.
After you finish in the browser, return to your and continue the original task. Arcade does not resume it for you.
You never give your agent an or a password for either layer. To check or manage connections, ask your to “Check my Arcade connection,” “Show my connected apps,” or “Connect Google.” You can connect an app before you need it. Clients that support Arcade commands also provide command shortcuts.
Arcade uses the app connections authorized for your signed-in identity. Authorize only the you intend the to use.
Next steps
- What’s included: plugin components and client support
- Connect to MCP clients: configure a client against a gateway you control
- Integrations catalog: every app and toolkit Arcade supports
- Agentic development: point your at these docs with
llms.txt