Plugin

Let any agent use Arcade. Ask for what you want and the right tool runs
across every app you've connected.
App sign-in happens in the browser. No API keys.

---

Try Arcade in your agent. This plugin is for calling tools and getting started with Arcade — connect apps, call tools, and explore what Arcade can do. For team-wide features (custom tool allowlists, fine-tuned governance, connecting your IDP, etc.), use the scale-arcade skill and the Arcade dashboard.

Install

Every client below gets the same arcade MCP server at https://api.arcade.dev/mcp/arcade. What else comes with it depends on the client — the full breakdown is in the support matrix.

Client	Install	Instructions
Cursor		cursor.md
Claude Code		claude-code.md
Claude Desktop		claude-desktop.md
VS Code		vscode.md
GitHub Copilot CLI		copilot.md
Codex / ChatGPT		codex.md
OpenCode		opencode.md
Any MCP client	https://api.arcade.dev/mcp/arcade	agent-plugins.md

Cursor and VS Code one-click badges add the gateway only. The linked guide installs the skills too.

This repository is already the Claude marketplace. From Claude Code:

claude plugin marketplace add ArcadeAI/arcade-plugin
claude plugin install arcade@arcade

For Claude Code and GitHub Copilot CLI, you can also use the cross-client CLI:

npx plugins add ArcadeAI/arcade-plugin

It does not finish Cursor, VS Code, or Codex by itself. Use the linked guides for those; the install guide explains the CLI's limits. The marketplace name is arcade. If you already installed an arcade marketplace from another repository, do not add this one too: Claude treats them as the same marketplace and the second install replaces the first. Use one install source per client to avoid duplicates.

Install the ChatGPT ZIP

This path requires a ChatGPT account with plugin upload access. For a managed workspace, an eligible owner or admin uploads the plugin; members install it from their workspace's plugin directory.

1. Open Arcade's official plugin releases in your browser.
2. Expand Assets on a release that includes the ChatGPT plugin and download arcade-chatgpt-{VERSION}.zip. Do not use GitHub's Source code (zip) download. If the ChatGPT ZIP is absent, that release does not include it. Keep the file compressed.
3. Open ChatGPT on the web in the account and workspace where you want to install Arcade. Use the plugin upload option available to your account and select the downloaded ZIP. For eligible workspace owners and admins, the path is Admin console → your workspace → Plugins → Add → Upload plugin.
4. Select Install plugin if prompted, then connect Arcade and sign in when prompted.

If you don't see an upload option, check your account's access or ask your workspace admin. Uploading a ZIP to an ordinary chat does not install it. This installation flow is separate from submitting a plugin for public publication.

Upload availability and where a plugin can run are separate. Plugins marked Desktop only require the ChatGPT desktop app.

See OpenAI's plugin installation guide.

What each client gets

	Tools	Skills	Subagent	Commands	Rule	Hooks
Cursor IDE / Cloud Agents	✅	✅	✅	✅	✅	—
Cursor CLI	✅	✅	✅	✅	—	✅
Claude Code	✅	✅	✅	✅	—	✅
Claude Cowork	✅	✅	✅	✅	—	partial
GitHub Copilot CLI	✅	✅	✅	—	—	✅
VS Code (Copilot sessions)	✅	✅	✅	—	—	✅
Codex / ChatGPT local runtime	✅	✅	—	—	—	—
OpenCode	✅	—	—	—	—	—
Claude Desktop	✅	✅	—	—	—	—
Any MCP client	✅	—	—	—	—	—

Skills are try-arcade and scale-arcade. The subagent is arcade-operator. Commands, hooks, and the Cursor rule are client-specific. Routing-hook support, client-version limits, and partial behavior are detailed in the support matrix.

Try it

• "What's on my calendar tomorrow?"
• "Summarize unread email from this week."
• "Draft a reply to that thread, then wait for me to send it."
• "What can Arcade do?"
• "We want this workflow on a team gateway. What should we set up?"
• /try-arcade or /scale-arcade
• /arcade-status — check the gateway, sign-in, and connected apps
• /arcade-connect google — connect an app ahead of time
• /arcade-apps — see or disconnect connected apps

Commands work in Cursor, Claude Code, and Cowork. The Cursor IDE doesn't list them in the / menu; see the support matrix.

Your assistant speaks intent to Arcade. You see the useful result, a sign-in link when an app isn't connected yet, and a confirmation prompt before anything is sent, created, or deleted.

Learn more

• Plugin docs — prerequisites, install for each client, and connecting apps. What's included lists what each client gets.
• Install guides — quick install + one page per client
• Client support matrix — what each install gets
• Arcade docs — product, APIs, SDKs, and setup. Agents can start from llms.txt.
• Arcade dashboard — org rollout, project gateways, identity, and tool policy (see scale-arcade).
• Architecture — package layout and execution model.
• Privacy: tasks run through Arcade's hosted gateway and the apps you connect — privacy policy, terms of service.
• Support: support@arcade.dev.

Plugin usage events (off in this build)

Claude Code and Copilot CLI include telemetry adapters, but TELEMETRY_ENABLED is false: this package sends no usage events and generates no telemetry hooks in client manifests. docs/telemetry.md describes the event contract, what would be stored locally when enabled, opt-outs, and the separate approval required before collection can be enabled. The Arcade MCP gateway remains the canonical source for request and tool-call telemetry. Adapter behavior is covered by in-process tests; see docs/telemetry.md for what CI does and does not exercise.

Develop

Agents editing this repo should read AGENTS.md. ARCHITECTURE.md lists the source files and what is generated from them. The dev tooling (package.json, scripts, and tests) lives in dev/, so installing the plugin doesn't install its packages.

cd dev
npm ci
npm run verify

Before the first verify, run the command in the "Download Cursor's validator" step of .github/workflows/check.yml from dev/. Cursor publishes its validator without a license, so the repository keeps no copy and no script downloads it.

verify runs:

• the tests: hand-written file checks, a stale-generated-file check, every hook command in every client's manifest, and the Claude plugin directory's documented rules (dev/test/directory-policy.test.mjs)
• claude plugin validate, then a real Claude Code install into a temporary config that fails if Claude Code ran a package install (dev/scripts/verify-claude-install.mjs)
• Cursor's plugin validator (dev/scripts/verify-cursor.mjs checks the downloaded copy's hash, then runs it)
• Codex and Copilot CLI checks (dev/scripts/verify-codex.mjs, dev/scripts/verify-copilot.mjs): neither client has a validate command, so these install the plugin into a temporary home and check that the client loaded every MCP server and skill

CI runs each of these as its own job (.github/workflows/check.yml). The check job waits for all of them and, on pull requests, for Cursor Bugbot. Branch protection on main requires check.

Release

Release Please opens a release PR on main with version bumps across VERSION, adapter manifests, and CHANGELOG.md. Merge that PR to tag v{VERSION} and create the GitHub release.

Configure paths in release-please-config.json. The workflow lives at .github/workflows/release-please.yml.

Each release also gets arcade-chatgpt-{VERSION}.zip, the package to upload in OpenAI's plugin portal for the ChatGPT and Codex directory. It holds the portable plugin only (plugin.json at the ZIP root, mcp.json, skills/, the logo, and LICENSE), with no hooks or other clients' folders. Build it locally with npm run package:chatgpt in dev/ (writes dist/ at the repo root); the build fails if the extensions.com.openai.interface listing breaks the portal's limits, such as the 30-character display name and subtitle (shortDescription). See OpenAI's submission guide.

License

MIT. Copyright (c) 2024–Present Arcade AI.