mcp-bridgekit vs filesystem
Side-by-side comparison to help you pick between these two MCP servers.
mcp-bridgekit by mkbhardwas12 | filesystem by modelcontextprotocol | |
|---|---|---|
| Stars | ★ 60 | ★ 85,748 |
| 30d uses | — | — |
| Score | 46 | 77 |
| Official | — | ✓ |
| Categories | AI / LLM ToolsDeveloper ToolsOps & Infra | File SystemDeveloper ToolsProductivity |
| Language | Python | TypeScript |
| Last commit | 3 mo ago | this month |
mcp-bridgekit · Summary
A bridge that converts MCP stdio servers to HTTP endpoints with session pooling and background job handling.
filesystem · Summary
A feature-rich MCP server for filesystem operations with dynamic directory access control.
mcp-bridgekit · Use cases
- AI chatbot with tool calling capabilities
- Multi-tenant SaaS platform with customer-specific MCP tools
- Long-running data processing that exceeds HTTP timeout limits
filesystem · Use cases
- Enable AI models to read and write project files during development
- Allow Claude or other MCP clients to browse and analyze codebases
- Provide secure sandboxed access to specific directories for content generation
mcp-bridgekit · Install
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-workerfilesystem · Install
Installation
Using NPX
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/path/to/allowed/directory"
]
}
}
}Using Docker
{
"mcpServers": {
"filesystem": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount", "type=bind,src=/path/to/allowed/dir,dst=/projects/allowed/dir",
"mcp/filesystem",
"/projects"
]
}
}
}VS Code Extension
Click the installation buttons in the README to install directly in VS Code.