MCP Client/Server using HTTP SSE with Docker containers
LocalAbout MCP Client/Server using HTTP SSE with Docker containers
This project is a minimal, Dockerized example of an MCP client and server communicating over HTTP SSE. It is intended for exploring the client-server pattern, with a client that lists tools or submits a query.
Key features
- 01Build client and server Docker images
- 02Run server in a container
- 03List tools with the client
- 04Submit a query to the client
Use cases
- 01Explore MCP client-server communication
- 02Test an HTTP SSE transport setup
MCP support
Demonstrates MCP client-server communication using HTTP SSE. The server and client are packaged as separate Docker containers.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Client/Server using HTTP SSE with Docker containers
Building client and server
docker build -t mcp-server:latest .
docker build -t mcp-client:latest .
Running the server
docker run -P --network host mcp-server:latest
Running the client
List tools:
docker run -P --network host mcp-client:latest
Get answer to a query:
docker run -P --network host mcp-client:latest "What is 99+201?"
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.