Bring Llm Workflows
to Claude Desktop
Learn how to connect FlowiseAI to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect FlowiseAI to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
FlowiseAI in Claude Desktop
FlowiseAI and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FlowiseAI to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.