tokio-prompt-orchestrator vs filesystem
Side-by-side comparison to help you pick between these two MCP servers.
tokio-prompt-orchestrator by Mattbusel | filesystem by modelcontextprotocol | |
|---|---|---|
| Stars | ★ 55 | ★ 85,748 |
| 30d uses | — | — |
| Score | 45 | 77 |
| Official | — | ✓ |
| Categories | AI / LLM ToolsDeveloper ToolsOps & Infra | File SystemDeveloper ToolsProductivity |
| Language | Rust | TypeScript |
| Last commit | 2 mo ago | this month |
tokio-prompt-orchestrator · Summary
Multi-core Tokio-native orchestration for LLM pipelines with MCP server support.
filesystem · Summary
A feature-rich MCP server for filesystem operations with dynamic directory access control.
tokio-prompt-orchestrator · Use cases
- Enterprise LLM API orchestration with provider failover and cost optimization
- Production LLM service with prompt injection protection and request deduplication
- Multi-model deployments with load balancing and adaptive worker pool sizing
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
tokio-prompt-orchestrator · Install
Add to your Cargo.toml:
tokio-prompt-orchestrator = "1.9"For Claude Desktop MCP integration, add to claude_desktop_config.json:
{
"mcpServers": {
"tokio-prompt-orchestrator": {
"command": "cargo",
"args": ["run", "--release", "--package", "tokio-prompt-orchestrator", "--", "--mcp"]
}
}
}filesystem · 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.