mcpo-docker

Created By
alephpiecea year ago
An example Docker image for mcpo, a tool that exposes MCP (Model Context Protocol) servers as OpenAPI-compatible HTTP endpoints for OpenWebUI.
Overview

What is mcpo-docker?

mcpo-docker is an example Docker image for mcpo, a tool that exposes MCP (Model Context Protocol) servers as OpenAPI-compatible HTTP endpoints for OpenWebUI.

How to use mcpo-docker?

To use mcpo-docker, clone the repository, copy the sample configuration files, and create a Docker container to start the servers. You can also build the Docker image from source.

Key features of mcpo-docker?

  • Exposes MCP servers as OpenAPI-compatible HTTP endpoints.
  • Easy setup with Docker.
  • Supports multiple MCP servers with separate endpoints.

Use cases of mcpo-docker?

  1. Integrating MCP servers with OpenWebUI.
  2. Developing applications that require context-aware interactions.
  3. Testing and deploying MCP servers in a containerized environment.

FAQ from mcpo-docker?

  • What is MCP?

MCP stands for Model Context Protocol, which allows for context-aware interactions in applications.

  • Is mcpo-docker free to use?

Yes! mcpo-docker is open-source and available under the MIT license.

  • How do I connect OpenWebUI to my MCP servers?

You can connect by adding the endpoint URL in the OpenWebUI settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
alephpiece
Star
2
Language
Dockerfile
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago