🧠 Model Context Protocol (MCP) - Server-Client Implementation

Name: 🧠 Model Context Protocol (MCP) - Server-Client Implementation
Author: parasjain2426

@parasjain2426

Repository

About 🧠 Model Context Protocol (MCP) - Server-Client Implementation

This is a basic MCP Server-Client Impl using SSE

#mcp #server-client #sse #fastapi

Basic information

Config

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

{
  "mcpServers": {
    "mcp_server_client_impl": {
      "command": "python",
      "args": [
        "main.py"
      ]
    }
  }
}

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 🧠 Model Context Protocol (MCP) - Server-Client Implementation?

A minimal prototype that implements a Model Context Protocol (MCP) system consisting of an MCP server and an MCP client, communicating via Server-Sent Events (SSE) over HTTP using FastAPI. It demonstrates lightweight tool invocation for educational or development purposes.

How to use 🧠 Model Context Protocol (MCP) - Server-Client Implementation?

Run the MCP server on port 8000 and the MCP client on port 5000, both using python main.py after installing dependencies from requirements.txt. The client exposes POST endpoints /upload_claim and /get_claim_details that invoke the corresponding tools on the server.

Key features of 🧠 Model Context Protocol (MCP) - Server-Client Implementation

FastAPI-based server and client with SSE transport
Two defined tools: upload_claim and get_claim_details
Client endpoints mirror server tools for easy invocation
Simple in‑memory data storage (resets on restart)
Minimal prototype suitable for learning or experimentation

Use cases of 🧠 Model Context Protocol (MCP) - Server-Client Implementation

Understanding how MCP works with SSE communication
Prototyping tool‑based claim upload and detail retrieval
Testing client‑server MCP interactions in a local environment
Educational demonstration of MCP tool invocation over HTTP

FAQ from 🧠 Model Context Protocol (MCP) - Server-Client Implementation

What is the intended use of this project?

It is a minimal prototype for development or educational use only, not production‑ready.

Where is data stored?

Data is stored in‑memory and will be lost if the server restarts.

What are the runtime requirements?

Python 3.10+ and the dependencies listed in requirements.txt: mcp[cli], fastapi, and httpx.

How does the client communicate with the server?

The client sends SSE HTTP requests to the MCP server to invoke a tool; the server streams the response back via SSE.

What transports or authentication are supported?

Only SSE over HTTP is used; no authentication mechanism is implemented.

Comments

More Other MCP servers

Activepieces

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

23.2K