MCP Multi-Server Demo with SSE Transport

Created By
fredrikp999a year ago
Example of using MCP servers, both over sdio + sse. Also using langchain-mcp
Overview

What is MCP Multi-Server Demo with SSE Transport?

This project demonstrates the use of the Model Context Protocol (MCP) with multiple servers utilizing different transport methods, specifically stdio and Server-Sent Events (SSE). It integrates with LangChain to create an agent capable of utilizing tools from both a math server and a weather server.

How to use MCP Multi-Server Demo?

To use this project, clone the repository, install the required dependencies, set up your OpenAI API key, and run the main application. The application will start the servers and allow you to perform queries.

Key features of MCP Multi-Server Demo?

  • Demonstrates the use of MCP with multiple servers.
  • Provides a math server for basic arithmetic operations.
  • Offers a weather server that simulates weather information.
  • Integrates with LangChain to create an intelligent agent.

Use cases of MCP Multi-Server Demo?

  1. Performing arithmetic calculations through the math server.
  2. Retrieving simulated weather information from the weather server.
  3. Extending the project to include more servers or functionalities.

FAQ from MCP Multi-Server Demo?

  • What programming language is used?

The project is developed in Python.

  • Do I need an OpenAI API key?

Yes, you need to set up your OpenAI API key to use the agent functionality.

  • Can I extend the project?

Yes, you can add more tools or servers and modify the agent for more complex queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fredrikp999
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago