open-webui/mcpo

A simple, secure MCP-to-OpenAPI proxy server

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 15th, 2026
Created on March 30th, 2025
Open Issues & Pull Requests: 56 (+0)
GitHub issues: Enabled
Number of forks: 496
Total Stargazers: 4,383 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.1 hours
Mean response time: 13.6 days
90th percentile: 38.3 days
Tracked items: 120

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 41
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 365 days
Stale 30+ days: 34
Stale 90+ days: 32

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • bug (68)
  • enhancement (8)
  • good first issue (2)
  • help wanted (2)
  • invalid (2)
  • can't reproduce (1)
  • documentation (1)
  • question (1)

Most active issues this week

Detailed Description

MCPO is a proxy server that bridges the Model Context Protocol and OpenAPI standards.

The tool solves the problem of integrating MCP servers with systems that expect OpenAPI interfaces. Rather than requiring direct MCP support, MCPO acts as an intermediary that translates MCP protocol communications into OpenAPI-compatible endpoints. This approach allows existing MCP servers to be exposed through a standard REST API surface, enabling broader compatibility with tools and platforms designed around OpenAPI specifications.

MCPO suits projects where you have MCP server implementations but need to integrate them into environments that only understand OpenAPI. This is particularly valuable in contexts where you want to leverage MCP's capabilities without requiring all downstream consumers to implement MCP client logic. The tool is designed with security as a stated concern, making it appropriate for scenarios where you need controlled access to MCP functionality through a standardized interface.

The project shows active development with regular commits and responsive maintenance patterns. The codebase demonstrates consistent attention to the proxy's core functionality, with updates addressing both the translation layer between protocols and the security posture of the server.