mcp-server-manager
MCP SSE Launcher
Documentation
MCP SSE Launcher
A Python-based management system for Model Context Protocol (MCP) servers that automatically wraps stdio-based servers with Supergateway to expose them as SSE endpoints, plus provides a web-based inspector for testing.
Key Features
- Auto-update - keeps MCP servers up-to-date automatically
- Background monitoring - restarts crashed servers automatically
- Web inspector - debug and test MCP servers via browser
- SSE conversion - wraps stdio servers for HTTP/SSE access
- AI assistant integration - works with Cursor, Claude Desktop, etc.
Quick Start
# 1. Install dependencies
pip install -r requirements.txt
# 2. Set up environment (copy .env.example to .env and add API keys)
cp .env.example .env
# 3. Start all MCP servers (with auto-restart)
make run-servers
# 4. Start web inspector for debugging
make run-inspector
# 5. View inspector at the URL shown in the outputCommon Use Cases
Debug a specific MCP server
# Start inspector (will show URL with auth token)
make run-inspector
# Visit the URL shown in output to test MCP serversAdd a new MCP server
# Add GitHub MCP server
python mcp_servers.py add \
--name github \
--cmd npx \
--args "-y @modelcontextprotocol/server-github" \
--env GITHUB_TOKEN=your_token_here \
--port 8094Use with Cursor AI
Add to `~/.cursor/mcp.json`:
{
"mcpServers": {
"filesystem": { "url": "http://localhost:8090/sse" },
"github": { "url": "http://localhost:8094/sse" },
"brave-search": { "url": "http://localhost:8096/sse" }
}
}Restart a problematic server
# Kill conflicts and restart specific server
make restart-server SERVER=githubRun without auto-restart (for development)
make run-servers KEEP_ALIVE=0What Happens Automatically
- Updates: npm packages and git repos are checked/updated before starting
- Port conflicts: conflicting processes are detected and can be killed
- Process monitoring: crashed servers restart up to 3 times
- Logging: each server logs to `/tmp/.log`
- Cleanup: all processes are properly terminated on exit
Available MCP Servers
The default config includes popular servers like:
- filesystem (8090) - local file access
- github (8094) - GitHub repository interaction
- brave-search (8096) - web search
- fetch (8093) - HTTP requests
- youtube (8092) - YouTube search/info
- memory (8100) - persistent memory
- puppeteer (8101) - web automation
Troubleshooting
# Check what's using server ports
make check-server-ports
# Kill conflicting processes on server ports
make kill-server-conflicts
# Stop servers (inspector stops with Ctrl+C)
make stop-servers
# View server logs
tail -f /tmp/filesystem.logConfiguration
Servers are defined in `mcp_config.json`. Environment variables use `${VAR}` syntax and are loaded from `.env`.
Example server config:
{
"name": "github",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {"GITHUB_TOKEN": "${GITHUB_TOKEN}"},
"port": 8094,
"server_type": "stdio"
}Frequently asked questions
What is mcp-server-manager?
mcp-server-manager is MCP SSE Launcher
How do I install mcp-server-manager?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is mcp-server-manager open source?
Yes — it is hosted on GitHub at https://github.com/OwenQian/mcp-server-manager and has 4 stars.
Related MCP tools
Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions with a self-hosted knowledge graph engine.
Automate browser based workflows with AI
Hindsight: Agent Memory That Learns
A privacy-first app that strips AI watermarks from content you own.
Agent framework and applications built upon Qwen>=3.0, featuring Function Calling, MCP, Code Interpreter, RAG, Chrome extension, etc.
The power of Claude Code / GeminiCLI / CodexCLI + [Gemini / OpenAI / OpenRouter / Azure / Grok / Ollama / Custom Model / All Of The Above] working as one.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP