mcp-bridgekit
by mkbhardwas12·★ 60·Score 46
A bridge that converts MCP stdio servers to HTTP endpoints with session pooling and background job handling.
Overview
MCP BridgeKit serves as an intermediary between web applications and MCP stdio servers, translating HTTP requests into stdio subprocess calls. It handles per-user session pooling, real timeout management with background job fallback, and provides a live dashboard for monitoring. The architecture ensures web chatbots, mobile apps, and other HTTP-based clients can leverage MCP tools despite not being able to spawn local subprocesses directly.
Try asking AI
After installing, here are 3 things you can ask your AI assistant:
When to choose this
Choose this when building web applications that need to integrate with MCP servers and require session management, timeout handling, and background processing.
When NOT to choose this
Don't choose this for simple MCP integrations that don't require HTTP bridging or if you need a solution without external dependencies like Redis.
Tools this server exposes
1 tool extracted from the README (low confidence)analyze_dataAnalyze data using a custom query
Note: No explicit tools section found in README. Tool name 'analyze_data' was inferred from example API call in the 'API Reference' section.
Comparable tools
Installation
Installation
# Clone & install
git clone https://github.com/mkbhardwas12/mcp-bridgekit.git
cd mcp-bridgekit
# Copy environment config
cp .env.example .env # edit if needed
# Install (pick one)
uv sync --dev # recommended
pip install -e ".[dev]" # alternative
# Start Redis (required for job queue)
docker run -d -p 6379:6379 redis:7-alpine
# Start server
uvicorn mcp_bridgekit.app:app --reload
# Start worker
mcp-bridgekit-workerCompare mcp-bridgekit with
Last updated · Auto-generated from public README + GitHub signals.