Arcade

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.

Ask for what you want: email, calendar, Slack, issues, docs, and more. Your agent picks the right tool across every app you've connected. Sign in once in the browser without ever handing your agent a key.

MCP Server · Agent Plugins 1.0.0 · MIT

Each client installs differently; the install guide has the one command for yours (Claude Code, Codex, Cursor, VS Code, Copilot CLI, Claude Desktop).

Any MCP client (including OpenCode):

https://api.arcade.dev/mcp/arcade

Cursor and VS Code also offer one-click MCP links (gateway only, no skills) in the install guides.

Every client gets the Arcade gateway. How much of the rest it loads (skills, the arcade-operator subagent, commands, hooks) depends on the client; see the support matrix.

• "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.

• 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.

Agents editing this repo should read AGENTS.md. ARCHITECTURE.md lists the source files and what is generated from them.

npm ci
npm run verify

verify runs:

• the tests: hand-written file checks, a stale-generated-file check, and every hook command in every client's manifest
• claude plugin validate
• Cursor's plugin validator (scripts/verify-cursor.mjs downloads it at a pinned commit)
• Codex and Copilot CLI checks (scripts/verify-codex.mjs, 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 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.

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