FlowMCP

What is FlowMCP?

FlowMCP is a schema-based framework that bridges existing web APIs (REST or GraphQL) with AI systems by standardizing interaction through the Model Context Protocol (MCP). It abstracts complex APIs into clean, structured schema definitions, enabling seamless AI-driven communication with external services.

How to use FlowMCP?

Create a schema in a .mjs file exporting a const schema = {} object with keys like namespace, routes, and handlers, then use FlowMCP.activateServerTools({ server, schema, serverParams }) to connect to an MCP server via a StdioServerTransport. Parameters are defined inline with Zod validation, and modifiers allow pre/post/execute-phase logic injection.

Key features of FlowMCP

• Schema-based integration with structured route definitions
• Modifier system for pre-, post-, and execute-phase handlers
• Inline parameters with Zod type enforcement
• Embedded test cases to verify real-world API interactions
• Text-based, human-readable output
• Activation via standard MCP server tools

Use cases of FlowMCP

• Integrate APIs like Chainlink, CoinGecko, or Etherscan with AI agents
• Test API interactions before deployment using built-in test cases
• Generate valid schemas automatically using an AI-based schema generator
• Bridge existing REST/GraphQL endpoints into the Model Context Protocol

FAQ from FlowMCP

What does FlowMCP do that alternatives don't?

FlowMCP provides a standardized schema format with versioned contracts, inline Zod validation, embedded tests, and a modifier system for pre/post processing—all optimized for AI-driven consumption via MCP.

What are the runtime requirements?

FlowMCP runs on Node.js and requires the @modelcontextprotocol/sdk and zod packages. Schemas are .mjs files exported with a specific structure.

Where does data live and how is authentication handled?

Data is fetched from external APIs at runtime; no local storage is used. Authentication is managed via environment variables specified in requiredServerParams, which are substituted into headers or root URLs as {{...}} placeholders.

Are there any known limits?

Multiline parameter definitions are not valid in version 1.2.2—all parameters must be single-line. Schema formatting must follow strict indentation (4 spaces) and line spacing rules.

What transport does FlowMCP use?

FlowMCP connects via StdioServerTransport from the MCP SDK, allowing local integration with MCP hosts over standard input/output.