What dependencies does FlowMCP require?
FlowMCP depends on the `@modelcontextprotocol/sdk`, Node.js, and the Zod validation library. It runs in any Node.js environment and connects via the standard I/O transport.
@a6b8
基本信息
A modular framework for building, validating, and testing REST API routes using declarative schemas and zod interfaces.
工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
FlowMCP is a framework that adapts existing web APIs (e.g., REST) into a standardized Model Context Protocol (MCP) interface, enabling AI systems to consume those APIs in a structured, testable, and semantically consistent way. It abstracts complex APIs into AI-friendly schema definitions and provides built-in tools for testing, validation, and pre/post processing.
Install the package, create a schema (.mjs file) following the documented structure, then activate it using FlowMCP.activateServerTools({ server, schema, serverParams }) in a Node.js script that creates an MCP server with StdioServerTransport. Environment variables (e.g., API keys) are passed via serverParams. Pre-built schemas are available in the community repository.
FlowMCP depends on the `@modelcontextprotocol/sdk`, Node.js, and the Zod validation library. It runs in any Node.js environment and connects via the standard I/O transport.
API keys and other secrets are passed as environment variables or via the `serverParams` object during schema activation, using `{{ENV_VAR}}` placeholders in the schema definition.
FlowMCP uses the Model Context Protocol with the `StdioServerTransport`; all communication happens over standard input/output.
Yes. The namespace key must be unique, alphanumeric only, and at most 24 characters. Route definitions require either GET or POST methods and must include a route path with optional dynamic inserts.
Schemas are local `.mjs` files in the project. Data is fetched from the external APIs defined in the `root` URL. No data is stored by FlowMCP itself.

Official Instatus MCP server. Ask what's down and why a monitor is failing, measure uptime for a period, see what went down and for how long, post and resolve incidents, schedule maintenance, put up general notices, see
Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works.
JiCo for Jira & Confluence: local MCP server for Jira Data Center - redacts personal data before the AI model, holds every write for approval

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP
Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott
评论