Supercharge your AI with FlowiseAI. Orchestrate complex LLM workflows via chat.
Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
FlowiseAI connects your agent to a self-hosted LLM platform, giving you direct control over complex AI workflows and RAG pipelines.
You can trigger specific chatflows with natural language, manage vector data ingestion, and monitor performance metrics—all through simple conversation. This MCP turns the back end of your chatbot into an actionable tool for your agent.
What your AI can do
Get chatflow details
Retrieves detailed technical information about one chatflow.
Get server version
Returns the current operational version of the Flowise server.
List ai assistants
Lists available OpenAI-style assistants configured in the system.
Sends natural language input to a specific LLM flow and returns the generated response.
Retrieves a list of all structured AI orchestration flows you've built.
Pulls the complete technical structure and metadata for any specific chatflow.
Programmatically pushes raw documents or data into your linked vector store for RAG context.
Lists configured credentials, global variables, and custom tools used by the platform.
Retrieves information like captured leads, user feedback, and active assistant profiles.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 CompatibleWaiting for input…
FlowiseAI MCP with 12 Tools
These tools let you programmatically interact with every aspect of your Flowise platform, from running predictions to managing data ingestion.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using FlowiseAI on VinkiusGet Chatflow Details
Retrieves detailed technical information about one chatflow.
Get Server Version
Returns the current operational version of the Flowise server.
List Ai Assistants
Lists available OpenAI-style assistants configured in the system.
List Chatflows
Lists all existing LLM orchestration flows accessible to the agent.
List Flowise Credentials
Lists the configured API credentials for the Flowise environment.
List Chat Feedback
Retrieves a list of user feedback submitted for a specific chatflow.
List Flow Leads
Lists records of captured leads generated by the chatflows.
List Marketplace Templates
Retrieves a list of available chatflow templates from the marketplace.
List External Tools
Retrieves a list of custom tools defined for the system.
List Flow Variables
Retrieves a list of global variables used across all flows.
Execute Chatflow Prediction
Runs a specific LLM flow prediction based on natural language input.
Upsert Vector Data
Pushes structured or raw data into the associated vector store.
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with FlowiseAI, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FlowiseAI. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Debugging complex AI pipelines is usually a nightmare of tabs and IDs.
Right now, if your chatbot logic breaks down, you have to jump into the Flowise UI. You're clicking through component menus, scrolling for flow IDs, and manually verifying credentials in separate sections just to understand why 'Prediction X' failed. It’s a slow, tedious process of copy-pasting identifiers.
With this MCP, that manual work vanishes. Instead of navigating UIs, you talk to your agent. You ask it, 'Show me the details for the RAG Assistant flow.' And boom—it pulls all the technical structure and metadata instantly. Your AI client handles the deep dive so you don't have to.
List Chatflows: Get a complete inventory of your LLM workflows.
Before, if you wanted to see what flows were available, you had to navigate the dashboard and visually scan all the active projects. If a flow was hidden or newly created, you might miss it until testing failed.
Now, just ask your agent to run `list_chatflows`. It returns an immediate, structured list of every single LLM orchestration flow you've built. You get instant operational visibility without clicking anything.
What your AI can actually do with this
Building sophisticated AI chatbots usually means juggling a bunch of UIs: one for testing flows, another for managing documents, and yet another for checking credentials. With this MCP, you skip all that clicking. Your agent talks directly to your Flowise setup, letting it run complex logic and interact with your LLM orchestration layer entirely through chat commands.
You can ask the system to execute a specific prediction flow using simple natural language. Need to add new knowledge? Just tell your agent to push data into the vector store. Want to see what credentials you've set up or list all existing workflows? It pulls that structure for you.
This means your AI client becomes more than just a chatbot; it’s an operational coordinator, giving you total visibility over everything running in your Flowise ecosystem, right within your preferred Vinkius-connected environment.
019dd0f3-05bd-711c-8949-d4ba8f888697 Here's how it actually works
The bottom line is you manage your entire LLM data pipeline and flow logic using conversational commands, without ever leaving your primary AI client interface.
Subscribe to this MCP and provide your Flowise Instance URL and API Key.
Your agent authenticates the connection, giving it immediate programmatic access to all defined endpoints.
You issue a natural language command—like 'list all chatflows' or 'run prediction for X'—and the agent executes the required tool call.
Who is this actually for?
This MCP serves developers who are tired of switching between multiple UIs to test, debug, and expand their chatbot logic. If you spend time copying flow IDs into separate testing consoles or manually checking API keys, this is for you.
Tests complex orchestration flows by triggering specific chatflows using natural language queries instead of writing boilerplate test code.
Automates document ingestion into vector stores directly from the agent, ensuring new knowledge is available for RAG pipelines without leaving their development workspace.
Monitors chatflow performance by listing captured leads and reviewing user feedback using simple AI commands to track bot effectiveness.
What Changes When You Connect
You don't have to manually check credentials. Use the list_flowise_credentials tool to instantly review all configured API keys and service tokens through a simple query.
Monitoring is fast. Instead of jumping into separate dashboards, you can use your agent to list captured leads with list_flow_leads and gather user feedback via list_chat_feedback in one conversation.
Testing flows becomes conversational. You bypass the Flowise UI by using execute_chatflow_prediction, letting your AI client run a flow and report the result immediately.
Data ingestion is automated. Use upsert_vector_data to feed new documents into the vector store, ensuring your RAG pipelines have current knowledge without leaving your chat interface.
System oversight is simple. The list_chatflows tool gives you a complete inventory of all active workflows, while get_chatflow_details lets you inspect their full technical makeup.
See it in action
Debugging an AI Agent
An AI developer needs to know why a complex bot failed. Instead of clicking through the UI, they ask their agent to run list_chatflows to get the IDs, then use get_chatflow_details on the suspected flow ID to see exactly where the logic might be broken.
Updating Knowledge Bases
A data team has just processed a new batch of legal documents. They instruct their agent to run upsert_vector_data immediately, pushing the raw content into the vector store associated with the 'Compliance Bot' chatflow.
Reviewing Marketing Funnels
A product manager needs a performance report. They ask their agent to use list_flow_leads, which instantly returns all captured leads and shows how many users interacted with the 'Lead Generator' flow.
Auditing System Settings
An operations engineer wants to verify what credentials are active. They simply ask their agent to use list_flowise_credentials, getting a clear, conversational list of all connected services.
The honest tradeoffs
Trying to manually trace flow dependencies
The user tries to figure out which variables are used in the 'Customer Support Bot' by opening the Flowise UI and clicking into every single component.
Don't click around. Ask your agent to use list_flow_variables first, then use get_chatflow_details on the specific flow ID you need information about.
Forgetting which data needs updating
The developer writes a new set of documents but forgets to run any command to inject them into the system's knowledge base.
Always remember to use upsert_vector_data with your raw document payload. This is how you make sure new context actually gets available for RAG predictions.
Running a prediction without knowing the flow ID
The user tries to execute a chatflow named 'Support Bot' but doesn't know its internal ID, leading to an API error.
First, run list_chatflows to get all existing workflow names and their corresponding IDs. Then use the correct ID with execute_chatflow_prediction.
When It Fits, When It Doesn't
Use this MCP if your primary need is deep orchestration control over an already established LLM platform (like Flowise). You should use it when you need to programmatically read the state of flows, write new data into vector stores, or execute complex, multi-step processes via chat. Don't use this if all you need is a simple text prompt/response cycle; for that, your agent might connect directly to an LLM endpoint. Only rely on basic tools like list_chatflows and execute_chatflow_prediction. If you just want to list the available templates, use list_marketplace_templates; don't try to run a prediction instead.
Questions you might have
How do I check credentials using the FlowiseAI MCP? +
You use the list_flowise_credentials tool. This instantly retrieves a list of all configured API keys and service tokens, letting you verify your connections without navigating the platform's settings.
Is `upsert_vector_data` for updating documents? +
Yes, it is designed specifically to push new data or updated documents into the vector store. This action ensures that the Retrieval-Augmented Generation (RAG) context is always current.
What if I need to run a prediction on an old flow? +
First, use list_chatflows to confirm the flow ID. Then, pass that ID and your prompt to execute_chatflow_prediction. Your agent handles the execution.
How do I list all my flows using the FlowiseAI MCP? +
Run the list_chatflows tool. It provides a clean, conversational summary of every active LLM orchestration flow you have set up in your environment.
How do I monitor user feedback for a chatflow using list_chat_feedback? +
You can retrieve specific user comments and performance data by calling list_chat_feedback. This lets you see how users are interacting with the flow, pinpointing confusing spots or common queries that need model refinement.
What is the purpose of get_server_version in this MCP? +
This tool reports the specific version of your Flowise instance. Checking the server version ensures your AI client and the underlying infrastructure are compatible, helping you quickly diagnose setup discrepancies.
Where can I check the available context parameters using list_flow_variables? +
list_flow_variables displays all global variables configured for your entire ecosystem. This is essential for understanding what external data or custom settings are accessible to every single chatflow running through the MCP.
How do I view the internal components of a flow using get_chatflow_details? +
get_chatflow_details pulls up the complete technical structure for one specific chatflow. This allows developers to inspect every connected component, variable, and logic branch without needing access to the original Flowise UI.
How do I find my API Key in Flowise? +
Log in to your Flowise dashboard and click on the API Keys tab in the sidebar to generate or copy your unique token.
Does this support multi-tenant instances? +
Yes! Ensure you provide the full Instance URL and the API Key corresponding to the specific environment you want to manage.
Can I push documents to vector stores via AI? +
Absolutely. Use the upsert_vector_data tool by providing the chatflow_id and the JSON payload containing your document data.
We've already built the connector for FlowiseAI. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.