Tools-only MCP server
The agent plugin ships more than : two skills, three commands, and the arcade-operator subagent, all of which need a client that loads agent plugins . Any client can still connect to the same gateway and get every tool on it without loading the rest of the plugin.
That is what this section covers. The gateway URL is:
https://api.arcade.dev/mcp/arcadeInstall it
- Claude Desktop installs the full plugin from a marketplace, or connects with only through a custom connector.
- Any other MCP client takes the gateway URL directly. Cursor and VS Code also have one-click links.
What you give up
Tools alone still do the work. What you lose is the part that helps your use them well:
- The skills teach your to turn “reply to that thread” into the right sequence of calls, and to walk you through a team rollout when you ask about one.
- The commands give you
/arcade-status,/arcade-connect, and/arcade-appsfor checking and managing connections without leaving your . - The subagent keeps search out of your main conversation, so it does not crowd out your actual work.
If your client supports plugins , you should install the full plugin instead.
Sign in
No . You authorize twice: your client signs you in to Arcade with your Arcade when it first connects to the gateway. 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. You can connect an app before you need it.
Arcade uses the app connections authorized for your signed-in identity. Authorize only the you intend the to use. Server-level and tool-level authorization covers the split in depth.
Next steps
- Install the agent plugin: use the client-native install for Cursor, Claude Code, VS Code, Copilot CLI, Codex, or Claude Desktop
- Connect to MCP clients: point a client at a gateway you control, with your own list
- From personal use to team rollout: what changes when a team depends on the workflow