Bring Llm Workflows
to Mastra AI
Learn how to connect FlowiseAI to Mastra AI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the FlowiseAI MCP Server?
Connect your FlowiseAI (self-hosted) instance to any AI agent and take full control of your LLM orchestration and RAG workflows through natural conversation.
What you can do
- Prediction Orchestration — Trigger specific chatflows and retrieve LLM-generated responses programmatically using natural language inputs
- Chatflow Management — List all orchestration flows and retrieve detailed technical structures and metadata to monitor your AI agents
- Vector Intelligence — Programmatically upsert documents or raw data into the vector stores linked to your chatflows to ensure high-fidelity context
- Component Oversight — Access server-wide credentials, custom tools, and global variables to manage your complete Flowise ecosystem
- Operational Visibility — Monitor user feedback, leads, and assistant profiles directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Enter your Flowise Instance URL and API Key
3. Start orchestrating your LLM flows from Claude, Cursor, or any MCP client
No more manual testing in the Flowise UI for every prediction. Your AI acts as your dedicated LLM operations and orchestration coordinator.
Who is this for?
- AI Developers — instantly test and trigger complex orchestration flows using natural language queries
- Data Engineers — automate document ingestion into vector stores without leaving your workspace
- Product Managers — monitor chatflow performance and review captured leads through simple AI commands
Built-in capabilities (12)
Trigger an LLM flow prediction
Get details for a specific chatflow
Get Flowise server version
List OpenAI-style assistants
List user feedback for a chatflow
List all LLM orchestration flows
List custom tools
List captured leads
List global variables
List configured credentials
List chatflow templates
Push data into a vector store
Why Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and FlowiseAI tool infrastructure. Connect 12 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add FlowiseAI without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every FlowiseAI tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
FlowiseAI in Mastra AI
FlowiseAI and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FlowiseAI to Mastra AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FlowiseAI in Mastra AI
The FlowiseAI MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Mastra AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FlowiseAI for Mastra AI
Every tool call from Mastra AI to the FlowiseAI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp