Workflows MCP Server
by popand
The Workflows MCP Server provides weather information for cities through a simple API, exposing a weather workflow as a set of tools consumable by agents. It offers both an MCP implementation and a simplified direct API for fetching weather data.
Last updated: N/A
What is Workflows MCP Server?
This server is a Model Context Protocol (MCP) server that exposes a weather workflow as a set of tools, allowing agents to fetch weather data for cities. It provides two approaches: an original MCP server implementation and a simplified direct API for easier integration.
How to use Workflows MCP Server?
To use the simplified API, start the server with node direct-server.js
and access the weather API at http://localhost:3000/api/weather?city=New%20York
. For the MCP approach, build the project with npm run build
and start the server with npm start
. Use the SSE and messages endpoints to interact with the server, ensuring to include the connection ID in your requests.
Key features of Workflows MCP Server
Exposes a
get-weather
tool for fetching weather dataProvides a
check-weather
prompt template for LLM integrationUses HTTP/SSE transport for communication with clients
Offers a simplified direct API for easier use
Integrates with OpenWeatherMap for weather data
Use cases of Workflows MCP Server
Integrating weather data into AI agents
Building conversational weather applications
Providing weather information to LLMs for context
Automating weather data retrieval and processing
FAQ from Workflows MCP Server
What is the MCP protocol?
What is the MCP protocol?
The README doesn't explicitly define MCP but it's a protocol for communication between models and context providers.
Which approach should I use?
Which approach should I use?
For immediate functionality, the simplified direct API approach is recommended.
What are the prerequisites for running the server?
What are the prerequisites for running the server?
Node.js 18 or higher and npm or yarn are required.
How do I get the connection ID for the MCP approach?
How do I get the connection ID for the MCP approach?
The connection ID is returned to the client in the initial SSE response when connecting to the /sse
endpoint.
What is the license for this project?
What is the license for this project?
The project is licensed under the MIT license.