Workflows MCP Server

🚀 Workflow MCP Server

This is a Model Context Protocol (MCP) server that provides city weather information through simple APIs.

✨ Features

• This server exposes workflows as tools for agents. In this implementation, a tool named get-weather is exposed to obtain weather information for any city.
• A check-weather prompt template is provided for easy integration with large language models (LLMs).
• It uses the HTTP/SSE transport protocol to communicate with clients.

🚧 Workflow Architecture

When the get-weather tool is invoked, a workflow is triggered:

1. Receive the city name as input.
2. Query the OpenWeatherMap service to obtain the current weather data for that location.
3. Pass the raw weather data to the LLM for interpretation.
4. Return a friendly, natural - language description of the current weather conditions.

This architecture enables accurate weather data retrieval and intelligent processing, providing weather information in a more conversational and understandable manner.

📝 Current Implementation Notes

Due to certain technical challenges related to the MCP protocol implementation, we offer two approaches:

1. Original MCP Server - A TypeScript implementation in the src directory, which may have some compatibility issues with the current SDK version.
2. Simplified Direct API - A simple JavaScript implementation in the root directory (direct-server.js and direct-client.js), providing a RESTful endpoint without using the MCP protocol.

To implement the functionality immediately, we recommend using the simplified direct API approach.

📋 Prerequisites

• Node.js 18 or higher
• npm or yarn

📦 Installation

1. Clone this repository.
2. Install the dependencies:

   npm install
   

💻 Usage - Simplified API Method

1. Start the server:

   node direct-server.js
   

2. The server will run on port 3000 and provide the following features:
   • Weather API: http://localhost:3000/api/weather?city=New%20York
   • Health check: http://localhost:3000/health
3. Run the client example:

   node direct-client.js
   

💻 Usage - MCP Method

This method requires building the TypeScript code and may have some compatibility issues:

1. Build the project:

   npm run build
   

2. Start the server:

   npm start
   

3. The server will run on port 3000:
   • SSE endpoint: http://localhost:3000/sse
   • Message endpoint: http://localhost:3000/messages?connectionId=YOUR_CONNECTION_ID
   • Health check: http://localhost:3000/health

Understanding the Connection ID

The connection ID is a unique identifier generated for each client session when connecting to the SSE endpoint:

• When a client connects to the /sse endpoint, the server generates a unique connection ID.
• This ID is returned to the client in the initial SSE response.
• The client must include this ID as a query parameter in all subsequent requests to the /messages endpoint.
• This allows the server to route responses to the correct client's SSE connection.

For example, if your connection ID is 1742761520489, you would make a tool call to the following address:

http://localhost:3000/messages?connectionId=1742761520489

📄 API Reference

Direct API

GET /api/weather

Get the weather information for a specified city.

Parameters:

• city (required) - The name of the city

Returns:

• Weather data, including information such as temperature and humidity

MCP Server

The documentation for this part is not yet complete. We will provide detailed information as soon as possible.