Workflows MCP Server

Created By
popanda year ago
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 server that provides integration through REST endpoints and Model Context Protocol (MCP) to a workflow engine, specifically designed to fetch and interpret weather information for cities.

how to use Workflows MCP Server?

To use the server, you can either utilize the simplified direct API approach or the MCP approach. For the direct API, start the server and access the weather API by providing a city name. For the MCP approach, build the TypeScript code, start the server, and use the provided endpoints for communication.

key features of Workflows MCP Server?

  • Exposes a get-weather tool for fetching weather data for any city.
  • Provides a check-weather prompt template for easy integration with LLMs.
  • Supports HTTP/SSE transport for client communication.

use cases of Workflows MCP Server?

  1. Fetching real-time weather data for various cities.
  2. Integrating weather information into applications using LLMs.
  3. Providing health check endpoints for monitoring server status.

FAQ from Workflows MCP Server?

  • What is the difference between the direct API and MCP approach?

The direct API is a simpler implementation that does not use the MCP protocol, while the MCP approach is a more complex TypeScript implementation that may have compatibility issues.

  • How do I fetch weather data for a city?

Use the endpoint http://localhost:3000/api/weather?city=CityName after starting the server.

  • What are the prerequisites for running the server?

You need Node.js 18 or higher and npm or yarn installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
popand
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago