Claude Wrap Mcp

io.github.Alex-KaffPublished by GitHub account Alex-Kaffv0.1.0Updated Oct 24, 2026

MCP server that spawns and drives Claude Code sessions via claude-wrap.

The publisher's own server: Claude Platform Docs

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

MCP server that spawns and drives real Claude Code sessions, letting an assistant run and supervise a fleet of Claude Code sub-agents.

What you can do
  • Start, list and stop Claude Code sessions, including discovered and tmux-backed ones
  • Send prompts and wait for idle, or push raw text, lines and keys without waiting
  • Inspect session state: busy status, mode, tokens, pending permission prompts, todos
  • Page through a session's tool calls and fetch one call's arguments and result by id
  • Read rendered transcript snapshots and approve or deny pending permission prompts
  • Drive non-interactive claude -p sessions that return structured JSON, usage and cost
When to use it
Useful when you want an assistant to orchestrate several Claude Code agents in parallel, hand long-running coding tasks to separate sessions, or monitor and answer permission prompts from a supervising agent.
Requirements
Runs locally over stdio as an npm package (claude-wrap-mcp). Needs Node 18 or newer and the claude CLI on PATH. Optional environment variables CLAUDE_WRAP_BACKEND=tmux, CLAUDE_WRAP_TMUX_ON_EXIT and CLAUDE_WRAP_REGISTRY configure the tmux backend; attaching to visible terminal windows is Windows-first.
Before you install
Spawned sessions run real Claude Code agents that can edit files and run commands in the given working directory, and claude_resolve_permission can approve those actions. claude_stop kills a tmux session. With the tmux backend, sessions outlive the server unless CLAUDE_WRAP_TMUX_ON_EXIT=kill is set, and any server can adopt them. Sessions consume Claude usage and cost.

Installation

In SourceWeft

  1. Open Claude Wrap Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

claude-wrap-mcp

[npm version] [license]

An MCP server that lets an agent spawn and drive real Claude Code sessions, so Claude Code can run a fleet of Claude Code sub-agents. Built on claude-wrap.

Needs Node ≥ 18 and the claude CLI on your PATH. Headless sessions work everywhere; attaching to visible terminal windows is Windows-first.

Install

sh
npm install -g claude-wrap-mcpclaude mcp add claude-wrap -- claude-wrap-mcp

Or in .mcp.json / claude_desktop_config.json:

json
{  "mcpServers": {    "claude-wrap": { "command": "npx", "args": ["-y", "claude-wrap-mcp"] }  }}

Tools

ToolWhat it does
claude_spawnStart a session in an absolute cwd. Returns a sessionId.
claude_askSend a prompt, wait for idle, return the transcript tail + parsed state.
claude_sendSend raw input (text / line / key) without waiting — for long tasks.
claude_statusBusy, mode, tokens, pending permission prompt, todos, last 5 tool names.
claude_tool_callsPage through the session's tool calls. Ids + names by default.
claude_tool_resultOne tool call by id: its args and result.
claude_snapshotThe rendered transcript lines.
claude_listEvery session, spawned here or discovered, with its backend, tmux attach command and lineage.
claude_resolve_permissionapprove / deny a pending permission prompt.
claude_stopShut down a session this server spawned or adopted (kills a tmux session).

There is a second family, claudep_*, that drives non-interactive claude -p sessions and returns structured JSON, tool calls, usage and cost.

Two things worth knowing:

  • Permission prompts are surfaced, not bypassed. When claude_ask or claude_status reports a permissionPrompt, answer it with claude_resolve_permission.
  • Tool calls are paged, not dumped. A status poll stays cheap because it carries only names; claude_tool_calls lists the rest and claude_tool_result fetches one call's output by id.

Sessions in tmux (Linux/macOS)

Set CLAUDE_WRAP_BACKEND=tmux in the server's environment (e.g. box-wide). claude_* sessions then run in tmux sessions, with no change to the MCP config:

  • they outlive this server: on shutdown it leaves them running, and anyone can tmux attach (the command is in claude_spawn / claude_list). Set CLAUDE_WRAP_TMUX_ON_EXIT=kill to stop them with the server instead;
  • any server adopts them: pass a tmux session name (as listed) as sessionId and the session is attached in-process, with full parsed state;
  • lineage: a session spawned from inside an agent that has TASK_ID / AGENT_ID set records that task and parent. claude_list shows it, and the registry entry (CLAUDE_WRAP_REGISTRY, one file per session when it's a directory) carries it for a supervisor.

See claude-wrap's README ("tmux backend") for the knobs and the entry format.

Develop

sh
pnpm installpnpm --filter claude-wrap-mcp buildpnpm --filter claude-wrap-mcp test

License

MIT © Alex Kaffetzakis

Source: README.md at commit a883d9e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Claude integrations