Workflows MCP Server
@popand
A server that provides an integration through both direct REST endpoints and Model Context Protocol (MCP) integration to a workflow engine.
Overview
What is Workflows MCP Server?
Workflows MCP Server is a Model Context Protocol server that exposes workflows as tools for agents. It includes a weather workflow with a get-weather tool and a check-weather prompt template, using HTTP/SSE transport for communication.
How to use Workflows MCP Server?
Install with npm install, then either run the simplified direct API with node direct-server.js (port 3000) or the MCP approach with npm run build then npm start. The MCP approach requires a connection ID from the SSE endpoint for bidirectional communication.
Key features of Workflows MCP Server
- Exposes the
get-weathertool to fetch weather data for any city. - Provides a
check-weatherprompt template for LLM integration. - Uses HTTP/SSE transport for client-server communication.
- Includes a simplified direct API for immediate functionality.
- Queries OpenWeatherMap and passes data to an LLM for natural language output.
Use cases of Workflows MCP Server
- Fetching current weather conditions in a conversational format via an agent.
- Integrating weather data into LLM-powered applications.
- Prototyping workflow-based MCP servers with tool and prompt templates.
FAQ from Workflows MCP Server
Why are there two approaches—MCP and direct API?
Due to technical challenges with current MCP SDK versions, the direct API offers a simpler, more reliable alternative for immediate use.
What are the runtime dependencies?
Node.js 18 or higher and npm or yarn are required.
Where does the weather data come from?
The server queries the OpenWeatherMap service for current weather data.
What transport protocols are supported?
The MCP approach uses HTTP with SSE; the simplified approach provides a plain RESTful endpoint.
Is authentication required?
The README does not mention any authentication mechanism; both approaches run without authentication.