Wrap and manage MCP servers with restartable proxying for seamless iterative development.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-wrap" yet — see the docs or source repo.
Use mcp-wrap to wrap my local MCP server, provide start, stop, and restart controls, and keep proxying its original tools and resources so I can change code without reconnecting the client.
A lifecycle-managed MCP wrapper that lets you restart the server during development while preserving proxied access.
I am iterating on an MCP toolset. Proxy the service through mcp-wrap and keep exposing the latest tools, resources, and notification interfaces after server restarts.
A proxy setup that continuously exposes the latest MCP capabilities after backend service updates.
Use mcp-wrap to add a unified start, stop, and restart entry point for an MCP service in my test environment while preserving its tool calls and notification forwarding.
A unified management entry point for testing and operations that controls service lifecycle and proxies original MCP interfaces.
Wrap any CLI tool as an MCP service for natural-language command execution.
Proxy multiple MCP servers while reducing token usage with on-demand tool loading.
Dynamically manage and invoke MCP servers without restarting your runtime.
Manage multiple MCP servers and load tool schemas on demand efficiently.
Securely proxy MCP services as OpenAPI endpoints for easier integration and deployment.
Add authenticated proxying, token management, and tool aggregation for MCP servers.