Skip to content

Tools and accounts · MCP, skills & plugins

Connect with context.

Connect MCP servers, let other MCP clients use SwarmPane, and understand tool access and what a Preview label means.

Give your agents MCP servers

Settings → MCP lists every MCP server your coding agents have (Claude Code, Codex, Cursor, OpenCode, Copilot, Grok and Gemini), with a chip for each agent. Click an agent that lacks a server to add it there, or one that has it to remove it; removing asks first. Add a server from the well-known ones (GitHub, Playwright, Context7, Supabase, Linear, Sentry, Notion, Chrome DevTools, Filesystem, Vercel, Stripe) or type your own command or URL, then pick the agents that get it. SwarmPane writes it into each agent’s own settings, saved accounts included.

A server is a command that runs on this computer or a service you sign in to, so review the command, its environment and the access it asks for before you add it. Keys stay on this computer; keep them out of shared instructions and screenshots.

Servers for Agent-mode teammates

SwarmPane’s Agent-mode teammates use their own servers, at the bottom of Settings → MCP under Servers for Agent-mode teammates. Each is a command SwarmPane runs when you verify it or run one of its tools; the coding agents in your panes don’t see these.

Discovery is only the first check

Discovering tool names means the server responded. It does not establish that every action is appropriate or will succeed. Inspect a tool’s input and result, and review consequential actions before running them.

The connector catalog can include Preview entries. A Preview listing is not an authenticated connection or proof that a working adapter is available.

Skills, plugins, and access

Settings → Skills shows the skills your agents load themselves: each a folder with a SKILL.md, in Claude Code’s, Codex’s and Grok’s own folders, for every project or one. Edit one, give it to another agent or take it away (Undo puts it back), or start one from a template; the description says when an agent should use it. Plugins (Preview) check that the service CLIs you use, such as GitHub, Stripe or Vercel, are signed in; actions through plugins aren’t built yet. Installing instructions does not grant a provider account or permission to act in external systems.

Let other agents use SwarmPane

The SwarmPane MCP Bridge, below the servers in Settings → MCP, lets Claude Code, Cursor or any MCP client list your teammates, create tasks, run routines and search your projects. It listens only on this computer and answers only requests that carry this install’s access token.

Orchestrate agents from Claude Code

In Settings → MCP → Orchestration, click Set up once: it adds the bridge to Claude Code and installs the /swarmpane skill. Then type /swarmpane in a Claude Code pane and describe the job. That Claude plans the work, opens worker panes (each in its own copy of the project on its own branch, and on another model such as Sonnet if you ask), gives each its part, waits for them and reads what they did.

Every worker is an ordinary pane you can watch, answer and stop. When Claude Code asks a worker to trust its folder or for a permission, the pane shows that it needs you; the planner is told so and never answers for you. Only agent panes can be opened or driven this way, never a plain terminal, and the switch in the same place turns it off.

Need a hand with your setup?TroubleshootingContact