Bloom MCP Wrapper
Universal wrapper for MCP servers to route API calls through Bloom proxy with automatic npm/file detection
Ask AI about Bloom MCP Wrapper
Powered by Claude Β· Grounded in docs
I know everything about Bloom MCP Wrapper. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
Bloom MCP Proxy Wrapper
A universal wrapper for Model Context Protocol (MCP) servers that routes all external API calls through the Bloom proxy platform, providing authentication, observability, and access control.
Simple and consistent usage for all MCP server types:
- NPM packages (e.g.,
@modelcontextprotocol/server-github,firecrawl-mcp) - Local scripts (e.g.,
./my-mcp-server.js) - No absolute paths required!
- Automatic environment detection (localhost for dev, production API for prod)
Installation
npm install -g bloom-mcp-wrapper
Quick Start
Add MCP servers to your Claude Desktop configuration using bloom-mcp-wrapper:
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "bloom-mcp-wrapper", "@modelcontextprotocol/server-github"],
"env": {
"BLOOM_AUTH": "your-bloom-auth-token",
"MCP_SERVICE_NAME": "github"
}
},
"firecrawl": {
"command":"npx",
"args": ["-y", "bloom-mcp-wrapper", "firecrawl-mcp"],
"env": {
"BLOOM_AUTH": "your-bloom-auth-token",
"MCP_SERVICE_NAME": "firecrawl"
}
},
"custom-local": {
"command": "npx",
"args": ["-y", "bloom-mcp-wrapper", "./my-custom-mcp-server.js"],
"env": {
"BLOOM_AUTH": "your-bloom-auth-token",
"MCP_SERVICE_NAME": "custom"
}
}
}
}
Environment Variables
BLOOM_AUTH(required): Your Bloom authentication tokenBLOOM_PROXY(optional): Custom proxy URL (defaults to localhost:8000 in dev, production API in prod)DEBUG(optional): Set tobloomto enable debug loggingNODE_ENV(optional): Set todevelopmentto force localhost proxy
How It Works
The wrapper:
- Auto-detects whether the target is an npm package or local file
- Spawns the MCP server using the appropriate method (
npxfor packages,nodefor files) - Intercepts all HTTP/HTTPS requests made by the MCP server
- Routes them through the Bloom proxy for authentication and monitoring
- Provides dummy API keys automatically (no need to configure service-specific keys)
Environment Detection
- Development/Debug: Routes to
http://localhost:8000whenNODE_ENV=developmentorDEBUGis set - Production: Routes to
https://api.bloomtechnologies.appby default
Features
β
Universal compatibility: Works with any MCP server
β
Zero configuration: No need to set up service-specific API keys
β
Auto-detection: Automatically handles npm packages vs local files
β
Environment-aware: Different routing for dev vs production
β
Debug-friendly: Comprehensive logging when needed
β
Lightweight: No external dependencies
Examples
NPM Packages (Scoped)
bloom-wrapper @modelcontextprotocol/server-github
NPM Packages (Unscoped)
bloom-wrapper firecrawl-mcp
Local Files
bloom-wrapper ./my-server.js
bloom-wrapper /absolute/path/to/server.js
With Debug Logging
DEBUG=bloom bloom-wrapper @modelcontextprotocol/server-github
Environment Variables
Required Variables
BLOOM_AUTH: Your Bloom authentication tokenMCP_SERVICE_NAME: The service name for permission checking (e.g., "github", "google_maps", "firecrawl")
Optional Variables
BLOOM_PROXY: Proxy URL (defaults to Bloom API)DEBUG: Set to "bloom" for debug logging
License
MIT
Support
For issues and questions, please visit: https://github.com/bloomtechnologies-app/bloom-mcp-proxy/issues
