Main

If you’re turning MCP tools into a product surface, BridgeKit helps with three hard parts:

• Isolation: run per-user sessions so one customer’s tool state can’t bleed into another’s.
• Timeouts: turn slow calls into queued jobs; return a job id and let the client poll/stream status.
• Ops: use the dashboard to observe active sessions, job backlog, and tool inventory during incidents.

README excerpt (verbatim)

MCP BridgeKit

Embeddable MCP stdio → HTTP bridge for web chatbots.

Turn any MCP stdio server into HTTP endpoints your web app can call. Per-user session pooling, real timeout handling with background job fallback, live dashboard.

Table of Contents

• What Is MCP BridgeKit?
• The Problem It Solves
• Use Cases & Scenarios
• Architecture
• Request Flow
• Key Features
• Quickstart
• Docker (Recommended)
• One-Click Deploy (Vercel)
• API Reference
• Concurrency Model
• Configuration
• Security (Auth & Rate Limiting)
• Push Notifications (Webhook & SSE)
• Connecting to Any MCP Server
• Embedding in Your App
• Project Structure
• TypeScript Version
• End-to-End Testing Guide
• Horizontal Scaling
• Full Architecture Docs
• License

What Is MCP BridgeKit?

MCP (Model Context Protocol) is an open standard that lets AI applications connect to external tools and data sources. MCP servers communicate over stdio (stdin/stdout) — which means they run as local subprocesses and speak JSON-RPC over pipes.

The problem: Web applications (React, Next.js, Vue, mobile apps) can't spawn local subprocesses. They only speak HTTP. There's a protocol mismatch.

MCP BridgeKit is the bridge. It sits between your web app and MCP stdio servers, translating HTTP requests into stdio subprocess calls and streaming results back:

Your Web App  ──HTTP──▶  MCP BridgeKit  ──stdio──▶  MCP Server (tool)
                         (this project)

FAQ

Q: Why not call MCP tools directly from the browser? A: Browsers can’t spawn stdio subprocesses; BridgeKit bridges HTTP ↔ stdio.

Q: What about slow tools? A: README describes background-job fallback to avoid 30s gateway timeouts.

Q: How do I discover tools? A: README mentions a live GET /tools/{user_id} endpoint for discovery.