MCP.so
ログイン

Docker Build and Deployment Guide (mcpo project) MCP Server

@flyfox666

基本情報

カテゴリ

クラウドとインフラ

ライセンス

MIT

トランスポート

stdio

作者

flyfox666

Docker Build and Deployment Guide (mcpo project) MCP Server について

An example Docker image for mcpo(with npm,curl,nodejs,uv Pre-Built;Pre-Built MCP:amap;baidumap;server-brave-search; tavily;fetch), a tool that exposes MCP (Model Context Protocol) servers as OpenAPI-compatible HTTP endpoints for OpenWebUI.

Docker Build and Deployment Guide (mcpo project) MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Docker Build and Deployment Guide (mcpo project) MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is mcpo?

mcpo (Model Context Protocol OpenAPI Proxy) is a containerized deployment using Docker and Docker Compose. It dynamically installs MCP server tools (Python uvx, Node.js npx) at startup based on a config.json, runs as a non-root user for security, and supports flexible pip and apt mirror configuration.

How to use mcpo?

Create a .env file with MCPO_API_KEY (required) and optionally PIP_SOURCE. Prepare a config.json with MCP server definitions. Build the image with docker-compose build [--no-cache] and start the service with docker-compose up -d. The container’s start.sh script installs dependencies and launches the mcpo service.

Key features of mcpo

  • Dynamic dependency installation at container startup.
  • Non-root user (appuser) execution for security.
  • Persistent volumes for config, logs, data, and caches.
  • Configurable pip source via PIP_SOURCE build argument.
  • Environment isolation per MCP tool installation.

Use cases of mcpo

  • Deploying mcpo with multiple MCP servers in a containerized environment.
  • Replicating deployments with pinned tool versions for reproducibility.
  • Running mcpo with custom pip mirrors to speed up builds.
  • Managing API keys securely via .env files.

よくある質問

1

Why do I see “npx: command not found” or “git: command not found”?

Ensure the Dockerfile installs `nodejs` and `git`, and that the `PATH` includes `/usr/bin`. Rebuild the image with `docker-compose build --no-cache`.

2

Why do I get “mkdir: cannot create directory '/root': Permission denied”?

The container runs as non-root user `appuser`. All cache directories are redirected to `/app` via `ENV` variables, and `start.sh` only creates directories under `/app`.

3

Why is pip not using my custom `PIP_SOURCE`?

Confirm the `.env` file contains `PIP_SOURCE` and that `docker-compose.yml` passes it as a build argument (`build.args`). The Dockerfile must receive it via `ARG PIP_SOURCE`.

4

Why are network and dependency installations slow or failing?

The Dockerfile uses an Aliyun mirror to accelerate `apt`. For Python packages, set `PIP_SOURCE` in `.env` to a domestic mirror. Node.js and uv installations still depend on network availability.

コメント

「クラウドとインフラ」の他のコンテンツ