Skip to Content
Get StartedAgent PluginOverview

Install the Arcade agent plugin

The Arcade agent plugin puts Arcade inside your agent with one command. Your agent gains access to thousands of tools for email, calendar, chat, issues, docs, and dozens of other apps. You authorize each app in the browser the first time it comes up. No to create, no gateway to configure.

Outcomes

Install the Arcade plugin in your agent and run your first task against a connected app.

Prerequisites

  1. Node.js  so you can run npx
  2. A supported : Cursor, Claude Code, VS Code, GitHub Copilot CLI, or Codex
  3. An Arcade

The plugin is built for personal use. When you are ready to put a workflow in front of a team, read from personal use to team rollout. You will want your own MCP Gateway with a curated list and your own identity provider.

Install

Terminal
npx plugins add ArcadeAI/arcade-plugin

The CLI detects the supported agents on your machine and installs to each one. To install to a single , pass --target:

Terminal
npx plugins add ArcadeAI/arcade-plugin --target cursor
npx plugins add ArcadeAI/arcade-plugin --target claude-code
npx plugins add ArcadeAI/arcade-plugin --target vscode
npx plugins add ArcadeAI/arcade-plugin --target copilot
npx plugins add ArcadeAI/arcade-plugin --target codex

To see what an install would write without changing anything:

Terminal
npx plugins discover ArcadeAI/arcade-plugin

Reload your afterwards if it does not pick up the plugin on its own. A couple of agents gate plugins behind a setting. Claude Code may ask you to enable it with claude plugin, and VS Code needs chat.plugins.enabled set to true.

Two things worth knowing if you use more than one . Codex and ChatGPT share a plugin directory, so one install covers both. And VS Code can discover a copy installed through GitHub Copilot CLI, so install in one place rather than both.

// todo: claude mcpb instructions

Using a client that does not load plugins? Those connect to the same gateway as a tools-only MCP server.

Sign in

Authentication happens in two layers:

  1. Into the gateway. Your client will ask you to authenticate when it first connects. You sign in to Arcade in the browser, and the client can reach the gateway from then on.
  2. Into each app. When a task needs Gmail, Slack, Linear, or anything else, your hands you a link that grants the scopes that task requires. Approve it once and Arcade holds the token for that app. You won’t need to authenticate that service again unless a later task requires greater scopes.

You never give your agent an or a password for either layer. Ask your to run /arcade-status to see what applications are currently enabled , or /arcade-connect google to authorize an app with the widest possible scope before you need it.

All of your tool calls, tokens, and secrets route through your own Arcade , isolated from every other user of that gateway. No one else’s can ever reach your apps, , or tokens.

Every Arcade gateway works this way, not just the one in the plugin. Server-level and tool-level authorization goes deeper on the split.

What you get in each agent

Every install connects to the same Arcade gateway and gets the same tools. What differs is how much of the rest of the plugin each can load.

| Agent | Tools | Skills | Subagent | Commands | Rule | Hooks | | -------------------- | :------------: | :----: | :------: | :------: | :—: | :---: | --- | -------------- | | Cursor | ✅ | 2 | ✅ | 3 | ✅ | ✅ | | Claude Code | ✅ | 2 | ✅ | 3 | — | ✅ | | Claude Cowork | ✅ | 2 | ✅ | 3 | — | ✅ | | GitHub Copilot CLI | ✅ | 2 | ✅ | — | — | — | | VS Code | ✅ | 2 | — | — | — | — | | Codex and ChatGPT | ✅ | 2 | — | — | — | — | | Any other client | ✅ | — | — | — | — | — | | // | Claude Desktop | ✅ | — | — | — | — | — | TODO: not true |

Here is what each of those is for.

Commands are the part you type. /arcade-status reports whether the gateway is reachable, whether you have signed in, and which apps you have authorized. /arcade-connect <app> authorizes an app on demand, so you are not interrupted mid-task. /arcade-apps lists what you have connected and lets you disconnect one.

Skills are instructions your reads on its own, so you never have to invoke them. try-arcade teaches it to turn a request like “reply to that thread” into the right sequence of calls across your apps. scale-arcade handles the other kind of question, the one about moving a workflow onto a team gateway, and it walks you through the decisions on this page against your own .

The subagent, arcade-operator, runs an app task in its own and reports back just the result. Arcade exposes a lot of , and searching them fills a conversation with noise that pushes out your actual work. The operator absorbs that.

The rule and hooks are Cursor and Claude Code specific. They tell your that Arcade exists and when reaching for it is the right move, which is the difference between a that sits unused and one your agent actually picks up.

The columns thin out because the Agent Plugins  1.0 specification only makes skills and servers portable. Commands, subagents, hooks, and editor rules are specific to each , so the plugin ships them where the agents that support them will find them.

Try it

The Arcade Plugin exposes hundreds of from our catalog that need zero additional configuration. Try asking your agent:

  • “Send a summary of tomorrow’s calendar events to me on Slack.”
  • “Read my Granola notes from last week, check them against Linear, and file anything I promised that is not a ticket yet. Wait for me before creating anything.”
  • “Find unread mail that needs a reply. Look the sender up in HubSpot if you can, draft a response, and Slack me the draft before sending.”
  • “Pull my open GitHub pull requests, my Linear issues, and tomorrow’s calendar. Write a standup update and send it to me on Slack.”
  • “Search my Drive and Notion for the latest product spec, then drop a one-paragraph summary in Slack.”

Or ask “What can Arcade do?” and pick a workflow from the answer.

\

Next steps

Last updated on
About ArcadeOverview