Oxide
Intelligent LLM orchestrator that automatically routes tasks to the most appropriate AI model (Gemini, Qwen, Ollama, LM Studio) based on task characteristics, enabling distributed processing and parallel execution across local and network services.
README
Oxide - Intelligent LLM Orchestrator
Oxide is an intelligent orchestration system that allows Claude Code to automatically route tasks to the most appropriate LLM based on task characteristics, enabling distributed AI resource utilization across local and network services.
Features
- Automatic Task Routing: Intelligently classifies tasks and routes them to the optimal LLM
- Parallel Execution: Distributes large codebase analysis across multiple LLMs simultaneously
- MCP Integration: Native integration with Claude Code via Model Context Protocol
- Multi-Service Support: Works with Gemini CLI, Qwen CLI, Ollama (local & remote), and LM Studio
- Web Dashboard: Real-time monitoring and configuration UI (coming soon)
Architecture
Claude Code (MCP) � Oxide Orchestrator � [Gemini | Qwen | Ollama | LM Studio]
Supported Services
Local Services:
- Gemini CLI: Large context window (2M tokens) - ideal for codebase analysis
- Qwen CLI: Code-specialized - best for code review and generation
- Ollama: Local inference - fast, low-latency queries
Network Services (LAN):
- LM Studio: OpenAI-compatible API on laptop
- Ollama Remote: Distributed processing on server
Installation
# Clone the repository
cd /Users/yayoboy/Documents/GitHub/oxide
# Install dependencies
uv sync
# Verify installation
uv run oxide-mcp --help
Configuration
Configure services in config/default.yaml:
services:
gemini:
type: cli
executable: gemini
enabled: true
qwen:
type: cli
executable: qwen
enabled: true
ollama_local:
type: http
base_url: "http://localhost:11434"
enabled: true
default_model: "qwen2.5-coder:7b"
Integration with Claude Code
Add to ~/.claude/settings.json:
{
"mcpServers": {
"oxide": {
"command": "uv",
"args": ["--directory", "/Users/yayoboy/Documents/GitHub/oxide", "run", "oxide-mcp"],
"env": {
"OXIDE_AUTO_START_WEB": "true"
}
}
}
}
Note: Setting OXIDE_AUTO_START_WEB=true automatically starts the Web UI when the MCP server launches!
Quick Start
Launch All Services
Multiple ways to start Oxide:
# Option 1: Unified launcher (MCP + Web UI)
uv run oxide-all
# Option 2: Auto-start Web UI with MCP (set OXIDE_AUTO_START_WEB=true in settings.json)
uv run oxide-mcp
# Option 3: Shell script
./scripts/start_all.sh
# Option 4: Separate services
uv run oxide-mcp # MCP server only
uv run oxide-web # Web UI only
See AUTO_START_GUIDE.md for detailed auto-start configuration.
Usage
Once integrated with Claude, use the MCP tools:
# Intelligent task routing
Use oxide route_task to analyze this code for bugs
# Parallel codebase analysis
Use oxide analyze_parallel to analyze the ./src directory
# Check service status
Use oxide list_services to show available LLMs
Task Classification
Oxide automatically classifies tasks:
- CODEBASE_ANALYSIS (>20 files or >500KB) � Gemini
- CODE_REVIEW ("review" keyword) � Qwen
- CODE_GENERATION ("generate"/"write" keywords) � Qwen/Ollama
- QUICK_QUERY (simple, no files) � Ollama Local
Web Dashboard
Oxide includes a real-time web dashboard for monitoring and control:
# Start backend server
uv run oxide-web
# Start frontend (in another terminal)
cd oxide/web/frontend && npm install && npm run dev
Access at http://localhost:3000
Features:
- Real-time service status monitoring
- Task execution history
- System metrics (CPU, memory)
- WebSocket live updates
- Service health checks
See WEB_UI_GUIDE.md for complete setup guide.
Network Services Setup
Configure remote LLM services on your LAN:
# Setup Ollama on another machine
./scripts/setup_ollama_remote.sh --ip 192.168.1.100
# Setup LM Studio on laptop
./scripts/setup_lmstudio.sh --ip 192.168.1.50
# Test network services
uv run python scripts/test_network.py --all
# Scan network for services
uv run python scripts/test_network.py --scan 192.168.1.0/24
Development Status
✅ Production Ready - MVP Complete!
- [x] Project structure and dependencies
- [x] Configuration system ✅
- [x] Adapter implementations ✅ (Gemini, Qwen, Ollama, LM Studio)
- [x] Task classification and routing ✅
- [x] MCP server ✅
- [x] Web UI dashboard ✅
- [x] Network services support ✅
- [x] Real-time monitoring ✅
- [ ] Test suite
- [ ] Production documentation
Requirements
- Python 3.11+
- uv package manager
- Gemini CLI (optional)
- Qwen CLI (optional)
- Ollama (optional)
License
MIT
Author
yayoboy esoglobine@gmail.com
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。