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.

Flowise MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: Flowise
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Flowise and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "flowise": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Flowise MCP Server

Connect your FlowiseAI instance to any AI agent and take full control of your low-code generative AI application development through natural conversation.

GitHub Copilot Agent mode brings Flowise data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Chatflow Orchestration — List and retrieve detailed architectural nodes and edges for all deployed Chatflows within your Flowise instance natively
Agentic Workflow Control — Access compound Agentflows defining complex AI tasks and multi-step reasoning logic synchronously
Live AI Prediction — Commands the backend to submit user questions to specific Chatflows and retrieve generated AI responses in real-time
Execution History Auditing — Pull precise past execution traces and conversational logs to debug logic chains and monitor agent performance limitlessly
Tool & Integration Discovery — Retrieve custom tools and third-party integrations configured in your Flowise environment to verify available capabilities
Credential Oversight — Enumerate stored credential components used to authenticate your AI logic chains securely within the platform
System Health Monitoring — Verify instance status and available base endpoints to ensure your AI orchestration layer is operational

The Flowise MCP Server exposes 7 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Flowise to VS Code Copilot via MCP

Follow these steps to integrate the Flowise MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Flowise

Ask Copilot: "Using Flowise, help me..." — 7 tools available

Why Use VS Code Copilot with the Flowise MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Flowise through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Flowise + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Flowise MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Flowise MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Flowise to VS Code Copilot via MCP:

get_chatflow

Get chatflow details

get_history

Get chat execution history

list_agentflows

List agentflows

list_chatflows

List chatflows

list_credentials

List credentials

list_tools

List available tools

predict

Run prediction on chatflow

Example Prompts for Flowise in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Flowise immediately.

"Ask chatflow 'abc-123': 'Summarize this document: [Context]'"

"List all active chatflows in my instance"

"Show me the execution history for chatflow 'Legal-Assistant'"

Troubleshooting Flowise MCP Server with VS Code Copilot

Common issues when connecting Flowise to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Flowise + VS Code Copilot FAQ

Common questions about integrating Flowise MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.