MCP server that spawns and drives Claude Code sessions via claude-wrap.
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.
npm install -g claude-wrap-mcp
claude mcp add claude-wrap -- claude-wrap-mcp
Or in .mcp.json / claude_desktop_config.json:
{
"mcpServers": {
"claude-wrap": { "command": "npx", "args": ["-y", "claude-wrap-mcp"] }
}
}
| Tool | What it does |
|---|---|
claude_spawn | Start a session in an absolute cwd. Returns a sessionId. |
claude_ask | Send a prompt, wait for idle, return the transcript tail + parsed state. |
claude_send | Send raw input (text / line / key) without waiting — for long tasks. |
claude_status | Busy, mode, tokens, pending permission prompt, todos, last 5 tool names. |
claude_tool_calls | Page through the session's tool calls. Ids + names by default. |
claude_tool_result | One tool call by id: its args and result. |
claude_snapshot | The rendered transcript lines. |
claude_list | Every session — spawned here or discovered. |
claude_resolve_permission | approve / deny a pending permission prompt. |
claude_stop | Shut down a session this server spawned. |
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:
claude_ask or
claude_status reports a permissionPrompt, answer it with
claude_resolve_permission.claude_tool_calls lists the rest and
claude_tool_result fetches one call's output by id.pnpm install
pnpm --filter claude-wrap-mcp build
pnpm --filter claude-wrap-mcp test
MIT © Alex Kaffetzakis
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y claude-wrap-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-alex-kaff-claude-wrap-mcp": {
"command": "npx",
"args": [
"-y",
"claude-wrap-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceclaude-wrap-mcpnpmio.github.Alex-Kaff/claude-wrap-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.