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 . Clients that do not, Claude Desktop among them, can still connect to the same gateway and get every tool on it.
That is what this section covers. The gateway URL is:
https://api.bosslevel.dev/mcp/all-optimizedInstall it
- Claude Desktop installs from a downloadable bundle, so you never paste a URL.
- 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, 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, and then each app gets authorized on its own the first time a task needs it. Approve that once per app and Arcade holds the token.
Your tool calls, tokens, and secrets route through your own Arcade , isolated from every other of the same gateway. Server-level and tool-level authorization covers the split in depth.
Next steps
- Install the agent plugin: one command for Cursor, Claude Code, VS Code, Copilot CLI, and Codex
- 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