How do I trigger a specific Flow XO workflow using the agent?

You can use the 'trigger_webhook' tool. Provide the Webhook URL generated by your Flow XO 'Webhook Trigger' and a JSON payload. The agent will post the data to that URL, starting the automated flow remotely.

What is a 'response path' and how do I get it?

A response path is a unique identifier for a user's conversation on a specific platform. You can find it by using the 'list_chatbot_users' or 'get_user_details' tools. It's required for sending push messages via the 'send_push_message' tool.

Can I disable a chatbot flow temporarily using the agent?

Yes! The 'toggle_workflow' tool allows you to enable or disable any of your flows by providing the Workflow ID and setting the 'active' parameter to true or false.

Flow XO MCP Server for VS Code Copilot 12 tools — connect in under 2 minutes

Name: Flow XO
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 12 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 Flow XO and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "flow-xo": {
      "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 Flow XO MCP Server

Connect your Flow XO account to any AI agent and automate your chatbot interactions and messaging workflows through the Model Context Protocol (MCP). Flow XO is a versatile platform for building and managing chatbots across various channels like Slack, Telegram, and the web. Now, you can manage your automation flows, oversee chatbot users, and trigger webhook-based workflows directly through natural conversation.

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

What you can do

Workflow Management — List all your chatbot flows and toggle their active status (enable/disable) instantly.
User Oversight — Access your end-user database, fetch detailed profiles, and create or update user records.
Direct Messaging — Send push messages directly to users via their unique response paths from your chat interface.
Webhook Triggers — Push data payloads to Flow XO webhook trigger URLs to start automated sequences remotely.
Interaction History — Retrieve the message history for specific users to understand past bot engagements.
Platform Connectivity — List all connected bot accounts and platforms (Slack, Messenger, etc.) for better integration context.
Automation Analytics — Fetch high-level usage summaries and performance metrics for your chatbot environment.

The Flow XO MCP Server exposes 12 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 Flow XO to VS Code Copilot via MCP

Follow these steps to integrate the Flow XO 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 Flow XO

Ask Copilot: "Using Flow XO, help me...". 12 tools available

Why Use VS Code Copilot with the Flow XO MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Flow XO 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

Flow XO + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Flow XO 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

Flow XO MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect Flow XO to VS Code Copilot via MCP:

create_user

get_automation_analytics

Get usage summary

get_user_details

Get user profile

list_bot_accounts

). List platform accounts

list_broadcasts

List sent broadcasts

list_chatbot_users

List all end users

list_user_history

List user messages

list_workflows

List automation flows

send_push_message

Send a push message

toggle_workflow

Enable/Disable a flow

trigger_webhook

Trigger flow via webhook

update_user

Update user metadata

Example Prompts for Flow XO in VS Code Copilot

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

"List all my Flow XO chatbot users."

"Disable the workflow 'Old Customer Survey'."

"Send a push message to path 'abc/123': 'Your order has been shipped!'."

Troubleshooting Flow XO MCP Server with VS Code Copilot

Common issues when connecting Flow XO 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.

Flow XO + VS Code Copilot FAQ

Common questions about integrating Flow XO 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.