OmniFix MCP Server
Enables LLMs to execute and validate autonomous multi-agent workflows with tools for workflow execution, output validation, and execution logging, plus resources and prompts for task decomposition and error recovery.
README
🚀 OmniFix — Autonomous Multi-Agent Workflow Automation
<div align="center">
A production-grade autonomous agent system that identifies, decomposes, and executes complex real-world workflows — with zero manual intervention.
🎮 Live Demo · 🏗️ Architecture · 🤖 Agents · 📄 Demo Pipeline
</div>
🎯 Problem Solved
Organizations waste thousands of hours on repetitive, fragmented workflows: invoice processing, document classification, data entry, multi-system notifications. OmniFix eliminates this entirely.
| Metric | Manual | OmniFix |
|---|---|---|
| Invoice processing time | ~25 minutes | ~8 seconds |
| Error rate | 3-8% | <0.5% |
| Human intervention | Always required | Only when confidence < 70% |
| Audit trail | Incomplete | Full evidence chain per step |
| Scalability | 1 person = 1 task | Unlimited parallel workflows |
🏗️ Architecture
graph TB
subgraph Dashboard["🖥️ OmniFix Dashboard (Dark Glassmorphism UI)"]
UI[Real-time Agent Graph] --> WS[WebSocket Events]
UI --> PIPELINE[Pipeline Visualizer]
UI --> LOGS[Live Log Stream]
end
subgraph API["⚡ FastAPI Gateway"]
REST[REST Endpoints] --> EXECUTE[/api/workflows/execute]
WS_EP[WebSocket /ws/events] --> BUS[Event Bus]
end
subgraph MCP["🔌 FastMCP Server"]
TOOL1[execute_workflow tool]
TOOL2[validate_output tool]
TOOL3[log_execution tool]
RES1[workflow://state resource]
PROMPT1[decompose_task prompt]
PROMPT2[error_recovery prompt]
end
subgraph GRAPH["🕸️ LangGraph StateGraph"]
PLANNER[🧠 PlannerAgent] -->|steps| EXECUTOR[⚙️ ExecutorAgent]
EXECUTOR -->|output| VALIDATOR[✅ ValidatorAgent]
EXECUTOR -->|error| RECOVERY[🔧 RecoveryAgent]
VALIDATOR -->|retry| EXECUTOR
RECOVERY -->|healed| EXECUTOR
end
subgraph SPECIALISTS["🤖 Specialist Agent Pool"]
DE[📝 DataEntryAgent<br/>Playwright + Forms]
DP[📄 DocProcessorAgent<br/>EasyOCR + LLM]
DM[🎯 DecisionAgent<br/>Rules + ML + HITL]
CA[📨 CommunicationAgent<br/>Slack + Gmail + Notion]
end
subgraph INFRA["🏗️ Infrastructure"]
REDIS[(Redis<br/>Workflow State)]
POSTGRES[(PostgreSQL<br/>History + Analytics)]
end
Dashboard -->|HTTP/WS| API
API --> MCP
MCP --> GRAPH
GRAPH --> SPECIALISTS
GRAPH --> INFRA
🤖 Agent Registry
Core Orchestration Agents
| Agent | Role | Key Capabilities |
|---|---|---|
| 🧠 PlannerAgent | Task decomposition | NL → atomic steps, LLM-powered, mock+real LLM |
| ⚙️ ExecutorAgent | Step dispatch | Concurrent execution, specialist routing, event emission |
| ✅ ValidatorAgent | Quality assurance | Evidence binding, schema validation, confidence scoring |
| 🔧 RecoveryAgent | Self-healing | Failure diagnosis, 5 recovery strategies, HITL escalation |
Specialist Agents
| Agent | Tools | Use Case |
|---|---|---|
| 📝 DataEntryAgent | Playwright, CSS selectors, ARIA | Web form automation, accounting software entry |
| 📄 DocProcessorAgent | EasyOCR, LLM, JSON schema | Invoice/contract classification + structured extraction |
| 🎯 DecisionAgent | Rules engine, ML model, DB query | PO validation, duplicate detection, approval routing |
| 📨 CommunicationAgent | Gmail API, Slack API, Notion API | Notifications, approvals, budget updates |
📄 Invoice Processing Demo
The flagship 8-step autonomous pipeline:
📧 Gmail Monitor → 🔍 OCR Extract → ✅ PO Validate → 💻 Accounting Entry
↓
📑 Report Generate ← 🗃️ Archive Drive ← 💬 Slack Approval ← 📊 Notion Budget
What happens automatically:
- Email Monitor — Scans Gmail inbox, detects invoice attachments
- OCR Extraction — EasyOCR + LLM extracts all fields with math validation
- PO Validation — Checks against purchase orders, applies 6 business rules
- Accounting Entry — Playwright fills all form fields, submits with confirmation
- Budget Update — Notion API updates project budget tracker
- Approval Request — Slack message to manager with structured invoice summary
- Archive — Google Drive upload with searchable metadata tags
- Report — Weekly processing summary generated and emailed
🔌 MCP Integration
OmniFix exposes a full Model Context Protocol server that any LLM can connect to:
# Tools
await client.call_tool("execute_workflow", {"workflow_name": "invoice_processing", "input_data": {...}})
await client.call_tool("validate_output", {"workflow_id": "abc-123", "expected_schema": {...}})
await client.call_tool("log_execution", {"workflow_id": "abc-123", "step": "OCR", "status": "success"})
# Resources
state = await client.read_resource("workflow://state/abc-123")
history = await client.read_resource("workflow://execution_history")
# Prompts
plan_prompt = await client.get_prompt("decompose_task", {"task_description": "process invoices"})
⚡ Quick Start
Option 1: Dashboard Only (Zero Setup)
# Just open in browser — works 100% offline!
start dashboard/index.html
Option 2: Full Stack (Docker)
git clone https://github.com/Soumo04/OmniFix-Autonomous-SRE-Remediation-Agent-.git
cd OmniFix-Autonomous-SRE-Remediation-Agent-
# Copy env (mock LLM works out of the box)
cp .env.example .env
# Launch everything
docker-compose up -d
# Open dashboard
start http://localhost:8000
Option 3: Local Python
pip install -r requirements.txt
# Start API server
python -m src.api.main
# (Optional) Start MCP server
python -m src.mcp_server.autoflow_mcp_server
# Open dashboard
start dashboard/index.html
🧪 Testing
# Install dev deps
pip install -r requirements.txt pytest pytest-asyncio
# Run all tests
pytest tests/ -v --tb=short
# Run with coverage
pytest tests/ --cov=src --cov-report=html
📁 Project Structure
OmniFix/
├── src/
│ ├── core/ # Config, logging, Redis/DB clients
│ ├── mcp_server/ # FastMCP server (tools/resources/prompts)
│ ├── orchestration/ # LangGraph StateGraph + routing
│ ├── agents/ # Base + 4 core + 4 specialist agents
│ └── api/ # FastAPI + WebSocket event bus
├── dashboard/
│ ├── index.html # Single-page glassmorphism dashboard
│ ├── css/ # Dark design system
│ └── js/ # D3 graph + real-time events
├── tests/ # Async pytest suite
├── docker-compose.yml # One-command stack launch
└── Dockerfile # Multi-stage build (api + mcp)
🏆 Key Innovations
- Evidence-Bound Reasoning — Every agent decision references specific data points; no hallucinations
- Self-Healing Graph — Recovery agent diagnoses failures and autonomously applies one of 5 strategies
- Progressive Authorization — HITL escalation only when confidence < 70%; fully autonomous above threshold
- MCP-Native — Standard protocol means any LLM (Claude, GPT, Gemini, Ollama) can orchestrate workflows
- Real-time Observability — WebSocket-powered dashboard shows live agent graph, confidence scores, and evidence chain
👥 Team
Built for the Intelligent Automation Hackathon — solving real-world repetitive workflow elimination with autonomous multi-agent AI.
<div align="center"> <strong>OmniFix — Because machines should handle the repetitive work.</strong> </div>
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。