ModelContextProtocolClient

Name: ModelContextProtocolClient
Author: InnoBridge

@InnoBridge

Repository

About ModelContextProtocolClient

Host with MCP client to call MCP servers for MCP development

#modelcontextprotocolclient #mcp-client #spring-boot

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

FAQ from ModelContextProtocolClient

What environment variables are required?

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

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.

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.