MCP servers and skills
MCP servers: one pool
Section titled “MCP servers: one pool”When a session starts, Swarmed reads the MCP servers set up for Claude Code, Codex and OpenCode, and in Swarmed itself, and gives the session’s agent the ones it lacks by name, as they are configured, secrets included. Nothing is copied into an agent’s own files.
| From | Read from |
|---|---|
| Claude Code | ~/.claude.json (your servers, and yours for the repository), the repository’s .mcp.json, and your user-scope plugins |
| Codex | ~/.codex/config.toml |
| OpenCode | ~/.config/opencode/opencode.json or opencode.jsonc |
| Swarmed | mcp.toml in the data directory, set up in Settings → MCP servers |
- Claude Code, Codex and OpenCode are not given a server by a name they already have, switched on or off. The configuration of other agents is not read, so they get the whole pool.
- Servers set up in Swarmed go to every agent, Claude Code included, in place of any of the same
name. Their secrets are kept in the Keychain, and
mcp.tomlholds only their names. - A server from the repository’s
.mcp.jsongoes to other agents only after you approved it in Claude Code, in your own settings rather than a file the repository tracks, and never once you rejected it. - An agent that cannot take HTTP servers gets only the ones it runs as programs.
shared_mcp_servers = falseon an entry inagents.tomlgives that agent only Swarmed’s own servers.
swarmed mcp lists the pool: the servers set up in Swarmed, Claude Code, Codex and OpenCode.
Skills
Section titled “Skills”A skill is a folder holding a SKILL.md. Swarmed reads them from:
~/.claude/skills,~/.codex/skills,~/.config/opencode/skillsand~/.agents/skills- Claude Code’s user-scope plugins
skills/in the data directory- the task’s own
.claude/skillsand.agents/skills
Each agent is offered the skills it does not read by itself, and /name calls one on any agent.
Settings → Skills can keep a skill from agents that don’t read it themselves.
swarmed skills --agent <id> lists what an agent would be offered.