MCP servers · alex-kaff

claude-wrap-mcp: MCP server for spawning and driving Claude Code sessions

An MCP server that lets an agent spawn, drive and monitor Claude Code sessions, including fleets of sub-agents.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server provides tools to start a Claude Code session in an absolute working directory, send a prompt and wait for the session to go idle, or send raw input without waiting. It also reports session status, pending permission prompts, todos and transcript lines, and lists sessions it spawned or discovered. A separate claudep_* family drives non-interactive claude -p sessions and returns structured JSON, tool calls, usage and cost.

It suits cases where one agent needs to hand work to other Claude Code sessions and follow their progress, including long tasks that are sent without waiting and checked later. Tool calls are paged, so status polling stays light, and permission prompts are surfaced to the caller to approve or deny rather than bypassed.

Running it requires Node 18 or later and the claude CLI on the PATH. Headless sessions work on any platform. Setting CLAUDE_WRAP_BACKEND=tmux runs sessions in tmux, where they keep running after the server stops, can be attached to from a terminal, and can be adopted by other servers. Session lineage is recorded from TASK_ID and AGENT_ID when they are set, and a registry can be written for a supervisor.

Limitations and requirements

Requires Node.js 18 or later and the claude CLI available on the PATH. Attaching to visible terminal windows is Windows-first, while the tmux backend is for Linux and macOS. Sessions run under tmux persist after the server shuts down unless CLAUDE_WRAP_TMUX_ON_EXIT=kill is set.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Alex-Kaff/claude-wrap-mcp

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

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
claude-wrap-mcp: MCP server for spawning and driving Claude Code sessions | AI Gate Discover