Flowise MCP for AI. Orchestrate AI workflows and debug history.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Flowise MCP connects your AI agent directly to a deployed FlowiseAI instance. You gain full command over low-code generative AI workflows.
This means running predictions, listing complex chatflows and agentflows, checking execution history, or auditing the credentials used by your systems—all from conversation with any compatible client.
What your AI can do
List chatflows
Retrieves a list of every deployed chat flow name and ID.
Get chatflow
Retrieves specific details about a single deployed chat flow.
Predict
Runs an immediate, simulated prediction by sending a user prompt to a specific chatflow.
List and get full details on every deployed conversational flow (Chatflow) within your Flowise instance.
Access detailed descriptions of complex, multi-step AI task chains defined by Agentflows.
Submit a user query to a specific chatflow and retrieve the generated AI response immediately.
Pull detailed records of past interactions, allowing you to trace logic chains and monitor agent performance over time.
Retrieve a list of custom functions and third-party integrations configured in your Flowise environment.
Ask an AI about this
Waiting for input…
Flowise MCP: 7 Tools
These tools let your agent interact with the back end of your Flowise system to manage workflows, check credentials, or test AI predictions.
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 Flowise on VinkiusList Chatflows
Retrieves a list of every deployed chat flow name and ID.
Get Chatflow
Retrieves specific details about a single deployed chat flow.
Predict
Runs an immediate, simulated prediction by sending a user prompt to a specific...
List Agentflows
Lists all available complex agent workflows (Agentflows) in the system.
List Tools
Retrieves a list of custom tools and third-party integrations available to the agent.
List Credentials
Enumerates all secure credentials components used by the Flowise platform.
Get History
Fetches the detailed execution log for a given chat session or workflow ID.
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 Flowise, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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 Flowise. 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 7 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking down AI failures used to mean diving through complex dashboards.
Remember when an agent gave a wrong answer? You had to jump into the Flowise UI, find the correct chatflow, click 'View History', and scroll through dozens of JSON logs just trying to figure out which node failed or where the context was lost. It's tedious, slow work that breaks your focus.
Now, you talk to your agent. You simply ask it to show the history for that specific flow. The agent uses `get_history`, pulls the clean log data, and presents exactly what happened—the inputs, the outputs, and where the chain broke. It’s instant troubleshooting.
Use Flowise MCP to get full visibility into your deployed assets.
Before this, figuring out what tools were even available meant clicking around multiple sections—checking the integrations list here, and then checking the tool nodes over there. You rarely got a single manifest of everything working together.
With Flowise MCP, you just ask your agent to run `list_tools` or `list_chatflows`. Everything is gathered into one accessible list. It's clean, direct, and immediately actionable.
What your AI can actually do with this
Need to debug an LLM pipeline without opening a dashboard? Flowise gives you that control. It connects your AI agent straight into your low-code generative AI development environment. Instead of relying on UI buttons, you just talk to your agent, and it handles the deep backend logic for you. You can list every chatflow or complex agent workflow you've built, run a test prediction on a specific flow instantly, and pull up precise logs of past executions.
If something breaks in production, your agent won't just guess; it will use tools to retrieve detailed history, pinpointing exactly where the logic chain failed. Because Vinkius hosts this MCP, you can manage these complex AI workflows from any client that supports the catalog.
019d759c-1af7-7384-a56b-3346493e0285 Here's how it actually works
The bottom line is you control complex AI pipelines using simple chat prompts, without ever leaving your agent interface.
Subscribe to this MCP and provide your specific Flowise Base URL and API Key. You find these keys in your Flowise Settings.
Your AI agent connects using the provided credentials, establishing a secure link to your internal Flowise environment.
You issue commands through natural conversation—for example, asking 'Show me the history for Legal-Assistant'—and your agent executes the required tool calls.
Who is this actually for?
This MCP targets developers and engineers who need visibility into their deployed generative AI systems. It's for the data scientist who can't trust a black box—the one who needs to verify exactly how an agent arrived at its answer by examining the execution history.
Debugging newly deployed conversational flows or multi-step agents. They use this MCP to run tests and retrieve chatflow details without rebuilding the entire environment.
Monitoring production agent health. They trigger predictions on live workflows and pull execution history when an automated process fails unexpectedly.
Auditing the scope of AI functionality. They use this MCP to list available tools or verify conversational logs to confirm the system is using all intended features.
What Changes When You Connect
You can test flows instantly. Use predict to submit a query to any chatflow, getting an immediate AI response without needing to manually set up test cases in the development UI.
Debugging is simplified by accessing the execution record via get_history. This allows your agent to pull precise logs and pinpoint exactly where a complex logic chain failed months after the fact.
Gain full architectural visibility. Instead of guessing, you can use list_chatflows and list_agentflows to see every deployed conversational asset in one place, confirming what's live in production.
Manage integrations securely. Use list_credentials and list_tools to verify which external APIs or custom functions your AI logic chain is actually authorized to call. No more guesswork on permissions.
Keep everything centralized. By connecting Flowise through Vinkius, you centralize control over multiple AI assets so your agent only needs one connection point.
See it in action
Debugging a knowledge base bot
A data scientist notices the legal chatbot is giving outdated answers. Instead of manually reviewing database connections, they use their agent to run get_history for that chatflow and immediately see the query logs showing which external document failed to load.
Verifying a new feature set
A product manager wants to confirm if the lead generation bot can access new CRM data. They prompt their agent, which uses list_tools and then runs a test prediction via predict, confirming the tool integration is live.
Auditing security risks
An automation engineer needs to know what credentials are available for an upcoming audit. They use their agent to call list_credentials and get a full, enumerated list of every API key stored in the system.
Checking complex logic flows
A development team is unsure if their new multi-step agent flow (Agentflow) works across all branches. They ask the agent to list_agentflows, select the target, and then manually trigger a test using get_chatflow details.
The honest tradeoffs
Asking for general AI help
Telling your agent, 'Fix my broken chatflow.' This is too vague. The agent won't know if you mean the code, the history, or the tools.
Be specific with a tool call. Say, 'Show me the execution history for Legal-Assistant,' using get_history. Or, say, 'List all my available tools,' using list_tools.
Assuming credentials are visible
Trying to guess if a specific API key is active or what it’s named. You can't see sensitive data just by looking at the flow list.
Always use list_credentials. This tool explicitly enumerates every stored credential component, giving you an auditable manifest of your system's access points.
Relying on UI buttons
Having to switch between the Flowise dashboard and your chat client just to test a flow. It breaks concentration and slows development down.
Keep it all in conversation. Use the predict tool to run live tests directly from your agent interface, keeping your workflow seamless.
When It Fits, When It Doesn't
Use this MCP if you need granular control over deployed AI assets. Specifically, you must be able to inspect why an agent acted a certain way by calling get_history, or you need to test live workflows using the predict tool before they go into production. It’s crucial for debugging and auditing. Don't use this if you just want to build a new chatflow; that requires the Flowise UI itself. If your goal is simply general LLM integration without needing deep visibility into flow architecture, a simple messaging API might suffice, but it won't give you the asset management of list_chatflows or the historical audit trail from get_history.
Questions you might have
How do I test a chatflow without using the Flowise UI? (predict) +
You use the predict tool. Just ask your agent to run a prediction on the specific chatflow ID you're targeting. It simulates the live user query and sends back the generated AI response in real-time.
What is the difference between list_chatflows and list_agentflows? (list_chatflows, list_agentflows) +
Chatflows manage conversations; Agentflows define multi-step tasks. Use list_chatflows to see basic conversation bots, and use list_agentflows to see complex processes that require multiple steps or decisions.
Can I find out what API keys are used by my AI agents? (list_credentials) +
Yes. Calling list_credentials will enumerate every secure credential component stored in your Flowise instance. It gives you a complete, auditable list of everything the agent can access.
How do I see what external APIs my flow uses? (list_tools) +
Run list_tools. This tool pulls all custom functions and third-party integrations configured in your Flowise environment, letting you verify exactly which capabilities are available to the agent.
How do I get the detailed architectural nodes and edges of a specific workflow using `get_chatflow`? +
The get_chatflow tool retrieves the full blueprint for any deployed chatflow. This lets you see every node and connection (edge), which is essential for understanding how data flows through complex logic chains.
If my AI agent fails, what do I use to track down where the error occurred? Should I use `get_history`? +
You must use get_history to debug failures. It pulls precise execution traces and conversational logs, showing you exactly which steps failed and why they broke down.
I need to verify what secrets are stored in the platform. How can I list all credentials using `list_credentials`? +
list_credentials enumerates every authentication component used by your AI logic chains. This gives you a central oversight of all stored API keys and connection details.
How do I check the structure and definitions for complex, multi-step agent tasks using `list_agentflows`? +
list_agentflows provides a manifest of your compound Agentflows. This lets you see the defined complexity and multi-step reasoning logic that powers your most advanced AI applications.
Can my agent run a prediction against a specific Flowise chatflow? +
Yes. Use the 'predict' tool. Provide the 'chatflow_id' and your question. The agent will command the Flowise backend to process the logic chain and return the AI-generated response directly in your chat.
How do I see the past conversational logs for a chatflow via chat? +
Use the 'get_history' tool with the 'chatflow_id'. Your agent will retrieve the past execution traces and logs, helping you understand how users have interacted with that specific logic chain natively.
Can I list all custom tools configured in my Flowise instance through the agent? +
Absolutely. Use the 'list_tools' tool. Your agent will retrieve custom tools and integrations configured in your environment, allowing you to audit available capabilities through natural conversation.
We've already built the connector for Flowise. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 7 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.