Skip to main content
MCP server CX Codex

magents — Claude Code MCP server: what it does, how to install

Connects independent assistant sessions through a shared local bus so tools can exchange context and hand off tasks without manual transcript copying.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add magents -- docker run -i --rm ghcr.io/abnegate/magents:0.14.2
Open on GitHub

What magents does

The server exposes a shared API over local disk transcripts produced by tools like Claude Code, Codex, and Cursor. It lets one assistant inspect what another was running, search previous dialog logs via search_transcripts, or inject prompts directly into an active thread through send_message.

For isolated workflows, spawn_session spins up headless background tasks with dedicated directories. Spawned agents strictly retain their host platform's confirmation prompts, which prevents circumventing user approval boundaries during execution.

What it helps with

  • transfer ongoing branch context directly between different coding tools
  • message another active agent session without manually copying errors
  • run headless background sessions inside isolated working directories
  • search local transcripts across multiple agent workspaces

Example prompts for the agent

  • Check current live sessions with magents and pick up the latest task from Codex
  • Search past assistant transcripts for mentions of migration errors
  • Launch an isolated background session to run tests in a separate folder

How to install magents

Platform CLI

claude mcp add magents -- docker run -i --rm ghcr.io/abnegate/magents:0.14.2

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about magents

How do I install magents in Claude Code?

Run claude mcp add magents -- docker run -i --rm ghcr.io/abnegate/magents:0.14.2 in your terminal. Restart your session so Claude Code loads the newly registered MCP tools.

What does magents do?

It acts as an inter-agent session bus. It enables coding assistants to read on-disk dialog logs, search shared memories, and route instructions to other active agents.

Does launching tasks with spawn_session bypass tool permissions?

No, headless sessions created by the tool enforce the native approval configuration of the host assistant. Security prompts are not bypassed.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor