The problem
How it works
In Langflow each project gets its own MCP server, and flows with a Chat Output component can be exposed as its tools. From the project’s MCP Server tab you choose which flows to serve, rename each tool and write a description, then copy a ready-made JSON snippet into your client’s MCP config or use the auto-install option. The documentation’s example exposes a Document Q&A flow about one person’s CV as a tool; when the user asks Cursor about that person, the agent picks the tool, and when they ask about someone else it explains that the tool does not cover them. Servers use streamable HTTP with SSE as a fallback, and authenticated servers get an API key per project.
Results and limitations
This is Langflow’s documentation with an illustrative example, not a reported project, so it is marked planned.
Before you try it
Langflow stresses tool names and descriptions: by default a tool is named after the flow’s ID, which tells an agent nothing, and vague descriptions make it pick the wrong flow. Turn on authentication before exposing a server beyond your machine, since anyone who reaches it can run your flows and spend your model credits. Tool calls time out after 180 seconds unless you raise the limit. Results depend on your setup and were not independently reproduced by Top 200 Repos.
Tools and repositories
- Tools
- Langflow · uv (mcp-proxy) · Cursor, Claude Desktop or another MCP client
- Prerequisites
- A Langflow server with at least one flow that ends in a Chat Output component.
Try it yourself: Write a tool name and description for a flow
Fill the fields to adapt the prompt. Empty fields stay as visible [placeholders].
I am exposing a Langflow flow to coding agents as an MCP tool. The flow [What the flow does], using [Data it uses]. It should be used when [When to use it] and never when [When not to use it]. Suggest a snake_case tool name and a description of at most three sentences that tells an agent exactly what the tool covers, what input it expects and what it returns.Ask the agent a question just outside the tool’s scope to check that it does not call it.
Related videos
About langflow-ai/langflow
This AI Tool Feels Like a Superpower! (opens in a new tab)
Walkthrough of langflow by DailyDev AI: its description links the GitHub repository.
Watch on YouTube (opens in a new tab)About langflow-ai/langflow
I Tested The Viral GitHub Repo That Replaces Expensive Closed AI (opens in a new tab)
Walkthrough of langflow by DailyDev AI: its description links the GitHub repository.
Watch on YouTube (opens in a new tab)Independent creators. Listing a video implies no endorsement, sponsorship or partnership.
Sources
- Use Langflow as an MCP server (opens in a new tab)
Project documentation · docs.langflow.org · Undated · Source checked 12 Nov 2026, 18:05 UTC
What this source supports
- Langflow adds each project to its MCP server and makes the project’s flows available as MCP tools; flows need a Chat Output component
- Flows can be enabled or disabled, renamed and described from the MCP Server tab
- Unclear tool names and descriptions can cause agents to select tools incorrectly; the default tool name is the flow ID
- Example of a Document Q&A flow used from Cursor, with the agent declining when the tool does not apply
- Streamable HTTP with SSE fallback, API key authentication, JSON and auto-install client setup, and a 180-second default tool timeout

