MCP.so
ログイン

MCPOSimpleServer MCP Server

@getsimpletool

基本情報

カテゴリ

その他

トランスポート

stdio

作者

getsimpletool

MCPOSimpleServer MCP Server について

MCP Calling Servere via SSE and OpenAPI

MCPOSimpleServer MCP Server の設定

標準の設定はありません

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

リポジトリ

MCPOSimpleServer MCP Server のツール

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

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

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

概要

What is MCPoSimpleServer?

MCPoSimpleServer is a lightweight, asynchronous API platform for running and managing MCP tools in isolated, secure environments. It implements the Model Context Protocol (MCP) for seamless integration with LLM applications.

How to use MCPoSimpleServer?

MCPoSimpleServer runs as a Docker container built on Debian 13 with a FastAPI/Python 3.13 server. Configuration is handled via a JSON file, and tools can be launched using uvx or npx. Users can define their own MCP servers with custom environment variables and access tools through SSE, Swagger REST, or OpenAPI endpoints.

Key features of MCPoSimpleServer

  • Local Docker container with a single SSE-MCP connection
  • Dynamic tool loading and filtering (whitelist/blacklist)
  • Access via SSE, Swagger REST, and OpenAPI.json (OpenWebUI‑compatible)
  • Each MCP server runs in its own thread for isolation
  • JSON‑based configuration – no database required
  • Bearer admin hack for simple authorization during testing

Use cases of MCPoSimpleServer

  • Running and testing MCP tools locally in a secure, containerized environment
  • Exposing MCP tools to LLM applications via standard APIs (SSE, REST)
  • Integrating with OpenWebUI through OpenAPI endpoints
  • Rapid prototyping and iteration with custom environment variables per tool
  • Selective tool exposure using dynamic whitelist/blacklist filtering

よくある質問

1

What is the Model Context Protocol (MCP)?

MCP is a protocol for integrating external tools with LLM applications; MCPoSimpleServer implements this protocol for tool management.

2

How are tools isolated from each other?

Each MCP server runs in its own thread, providing process‑level isolation within the Docker container.

3

What transport protocols are supported?

MCPoSimpleServer exposes tools via SSE, Swagger REST, and OpenAPI.json endpoints.

4

Does MCPoSimpleServer require a database?

No, it uses a JSON‑based configuration file for easy editing and portability.

5

What authorization method is used?

A configurable Bearer admin hack provides simple admin authorization, ideal for testing and quick changes.

コメント

「その他」の他のコンテンツ