Dell Enterprise MCP Workflow Proxy

Dell Enterprise MCP Workflow Proxy

An air-gapped, edge-native, deterministic translation layer that ingests raw Dell OpenAPI endpoints, clusters them into high-level workflows using a local offline LLM, and executes them deterministically at runtime via FastMCP and HTTPX.

Category
访问服务器

README

Dell Enterprise MCP Workflow Proxy

An air-gapped, edge-native, deterministic translation layer. This system ingests 500+ raw Dell OpenAPI endpoints, clusters them into high-level workflows using a local offline LLM, and executes them deterministically at runtime via a FastAPI + FastMCP ASGI microservice backed by SQLite and SQLAlchemy.


Architecture Overview

The system design separates ingest/clustering compile-time phases from the stateful runtime translation execution:

flowchart TD
    subgraph Compile-Time Phases
        A[Raw OpenAPI Specs] -->|Phase 1: Ingestion| B[OpenAPI Parser]
        B -->|OpenAPI schemas| C[AI Clustering Engine]
        C -->|Local Ollama/Instructor| D[(SQLite governance.db)]
    end
    subgraph Runtime Execution
        E[MCP Clients] <-->|SSE /mcp| F[FastAPI ASGI Server]
        G[(SQLite mcp_proxy.db)] <-->|SQLAlchemy Async| F
        F -->|Select Executor| H[BaseExecutor Interface]
        H -->|MockHTTPXExecutor| I[Prism Mock API / Redfish Endpoint]
        H -->|DellOMSDKExecutor| J[Real Dell Hardware]
    end

Core Architecture Principles

  1. Stateful Persistence: All workflows and API steps are stored in a SQLite database (mcp_proxy.db) using SQLAlchemy async models, replacing legacy static JSON configuration files.
  2. Governance and Approvals: Incoming clustered workflows remain pending until promoted to approved status through admin webhook REST APIs.
  3. Dynamic Hot-Reloading: Approved workflows are loaded dynamically as tools into FastMCP without restarting the ASGI server, and connected clients are notified in real-time.
  4. Resilience & Fault Isolation: Asynchronous HTTP executions employ exponential backoff retries via tenacity specifically targeting transient network issues.

Project Directory Scaffolding

dell_mcp_proxy/
├── data/
│   ├── raw_specs/              # Downloaded raw Dell OpenAPI YAML/JSON specs
│   └── output/                 # Runtime persistence store: mcp_proxy.db
├── src/
│   ├── __init__.py
│   ├── core/                   # Shared Pydantic models, configurations, and exceptions
│   │   ├── __init__.py
│   │   ├── config.py
│   │   ├── database.py         # SQLAlchemy schemas, engines, and async sessions
│   │   └── exceptions.py       # Custom exceptions hierarchy (e.g. DellProxyExecutionError)
│   ├── parser/                 # Phase 1: OpenAPI spec parsing and schema extraction
│   │   ├── __init__.py
│   │   └── openapi_parser.py
│   ├── ai_clustering/          # Phase 2: Offline clustering via Instructor/Ollama LLM
│   │   ├── __init__.py
│   │   └── workflow_generator.py
│   └── proxy/                  # Phase 3: FastAPI + FastMCP Server & Deterministic Routing
│       ├── __init__.py
│       ├── server.py           # FastAPI server initialization, webhooks, & dynamic tool registration
│       └── executors/          # Target execution engines
│           ├── __init__.py
│           ├── base.py         # BaseExecutor Abstract Base Class
│           └── httpx_executor.py # HTTPX executor implementation with tenacity retry loops
├── tests/
│   ├── __init__.py
│   ├── conftest.py             # Pytest fixtures and mock clients
│   ├── test_microservice.py    # Integration tests for webhooks, DB states, and reload behavior
│   └── test_mock_api.py        # HTTP mock container validation
├── .env.example                # Local environment template variables
├── .flake8                     # Flake8 style config
├── pyproject.toml              # Project dependencies, packaging, and tool overrides
└── README.md                   # System documentation

Technical Stack & Dependencies

  • Language: Python 3.10+
  • Dependency & Environment Manager: uv
  • ASGI & Web Framework: fastapi and uvicorn
  • MCP Framework: fastmcp (using ASGI/SSE transport)
  • Database & ORM: sqlalchemy (v2.0) and aiosqlite
  • Resilience Engine: tenacity (exponential backoff & async retries)
  • Code Quality: black, flake8, mypy, pytest

Getting Started & Local Setup

1. Prerequisites

Ensure you have Python 3.10+ and uv installed. If you do not have uv, install it via:

curl -LsSf https://astral.sh/uv/install.sh | sh

2. Environment Setup

Initialize the virtual environment and install all dependencies:

# Sync environment and lock dependencies
uv sync

3. Environment Variables

Copy the template variables file:

cp .env.example .env

Running the ASGI Microservice

1. Start the Server

Start the Uvicorn application (which hosts both the REST endpoints and the MCP SSE interface):

uv run uvicorn src.proxy.server:app --host 0.0.0.0 --port 8000 --reload

2. REST Admin Webhooks

  • Get Pending Workflows:
    curl -X GET http://localhost:8000/workflows/pending
    
  • Approve a Workflow:
    curl -X POST http://localhost:8000/workflows/{id}/approve
    
  • Reject a Workflow:
    curl -X POST http://localhost:8000/workflows/{id}/reject
    
  • Trigger Hot-Reload: Reloads the tool list from database state and notifies connected MCP clients:
    curl -X POST http://localhost:8000/reload
    

3. Connect to the MCP Server

Clients can connect to the Model Context Protocol endpoint using SSE (Server-Sent Events) at:

http://localhost:8000/mcp

Testing & Mock API Setup

To safely test workflows locally without breaking real hardware, we utilize a Stoplight Prism Docker container that mocks the realistic Dell iDRAC OpenAPI schema on port 4010.

1. Start the Mock Server

Ensure Docker is running, then boot the mock API container:

docker compose up -d --build

2. Run Automated Verification Pipeline

Execute the all-in-one automation script to sync dependencies, restart the mock server, verify health, run all pytest suites, and check code style:

chmod +x test_all.sh
./test_all.sh

Code Quality & Verification Commands

All files conform to strict enterprise quality checks. Verify your changes using:

# Code Formatting (Black)
uv run black --check .

# Code Linting (Flake8)
uv run flake8 .

# Strict Type Checking (Mypy)
uv run mypy .

# Run Tests
uv run pytest

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选