MCP.so
ログイン

ModelContextProtocolClient MCP Server

@InnoBridge

基本情報

カテゴリ

その他

トランスポート

stdio

作者

InnoBridge

ModelContextProtocolClient MCP Server について

Host with MCP client to call MCP servers for MCP development

#modelcontextprotocolclient#mcp-client#spring-boot

ModelContextProtocolClient MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "ModelContextProtocolClient": {
      "command": "docker",
      "args": [
        "compose",
        "up"
      ]
    }
  }
}

ModelContextProtocolClient MCP Server のツール

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

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

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

概要

What is ModelContextProtocolClient?

A Spring Boot client application that demonstrates different transport methods (WebFlux SSE, Stdio) for communicating with an MCP server. It can also interact with the BraveSearch API and a Weather API through configurable transports.

How to use ModelContextProtocolClient?

Set up a .env file with API keys, clone the required server repository, then use Docker Compose to start both containers. Build and run the server inside one container, then build and run the client inside another. The client exposes HTTP endpoints for each transport to list tools and perform calculations or weather lookups.

Key features of ModelContextProtocolClient

  • Supports WebFlux SSE, Stdio, and BraveSearch transports
  • Exposes REST endpoints for listing tools and invoking actions
  • Integrates with a calculator tool and a weather API
  • Runs inside Docker alongside an MCP server

Use cases of ModelContextProtocolClient

  • Demonstrate how a Spring Boot client can communicate with an MCP server using Server-Sent Events
  • Show Stdio-based client-server interaction by launching the server jar automatically
  • Test the BraveSearch API via a dedicated transport endpoint

よくある質問

1

What environment variables are required?

`BRAVE_SEARCH_API_KEY` and `WEATHER_API_KEY` must be set in a `.env` file in the root directory.

2

How do I start the client?

After cloning the required server repository and setting up Docker, run `docker compose up`, then exec into the server container to build and run it, then exec into the client container to build and run it.

3

What endpoints are available?

The client provides separate endpoints for each transport, e.g., `GET /webflux/tools`, `POST /webflux/calculate`, `POST /stdio/weather`, `POST /bravesearch`.

4

Which transports are supported?

WebFlux SSE (default), Stdio (launches server jar in stdio mode), and BraveSearch (uses an API key).

コメント

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