2,500+ MCP servers ready to use
Vinkius

Flock MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 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.

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 Flock and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "flock": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Flock
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 Flock MCP Server

Connect your Flock bot to any AI agent and take full control of your team communication, private groups, and organizational roster through natural conversation.

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

What you can do

  • Rich Messaging Orchestration — Provision massively fast payloads strictly into Flock chats, utilizing ` to render rich enterprise attachments and formatted layouts natively
  • Public Channel Discovery — Enumerate explicitly attached public channels and execute bulk iterations to capture global namespaces and routing configurations synchronously
  • Private Group Management — Identify bounded private groups and retrieve precise physical definitions detailing exactly how hidden groups operate within your enterprise
  • Organizational Roster Auditing — Discovers global identity blocks mapping direct @` aliases to absolute string UUIDs to solve accurate routing for the entire company
  • Identity Metadata Retrieval — Perform structural extraction of profile metadata linked to Flock users, resolving time zones and LDAP/SSO properties securely
  • Chat Log Ingestion — Pull chronological asynchronous logs from any room, extracting raw JSON objects mapping historical strings natively from chat fetchers
  • Membership Oversight — Audit IAM boundaries and identify explicit active UUIDs directly attached to channels or groups to verify intended audiences flawlessly

The Flock MCP Server exposes 10 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 Flock to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Flock

Ask Copilot: "Using Flock, help me...". 10 tools available

Why Use VS Code Copilot with the Flock MCP Server

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

01

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

02

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

03

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

04

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

Flock + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Flock MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Flock to VS Code Copilot via MCP:

01

channels_get_info

Retrieve explicit Channel descriptions and banner logic mappings

02

channels_list_members

Identify explicit Active UUIDs directly attached evaluating Channel ingress

03

channels_list_public

Enumerate explicitly attached `public` channels active within Flock

04

chat_fetch_messages

Extracts raw JSON objects mapping historical strings natively returned by `chat.fetchMessages`. Read recent structural Chat payloads targeting a Flock Room

05

chat_send_message

Detects if formatted `<flockml>` definitions are passed and converts the payload dynamically bypassing standard Markdown limits rendering rich enterprise attachments. Provision a massively fast payload strictly into an established Flock Chat

06

groups_get_info

Inspect deep internal credentials identifying a precise Private Group

07

groups_list_members

Crucial for verifying sensitive message targets. Audit IAM boundaries explicitly granting read permissions to a Group

08

groups_list_private

Returns arrays necessary to retrieve correct routing UUIDs. Identify bounded Private Groups tracking strict IAM boundaries

09

roster_list_directory

Returns explicit array definitions mapping direct `@` aliases to absolute string UUIDs solving accurate routing natively. Identify precise active Human constraints navigating the entire Flock company

10

users_get_metadata

Perform structural extraction of metadata linked to a Flock Identity

Example Prompts for Flock in VS Code Copilot

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

01

"Send a message to group 'g:123': 'Project update is live!'"

02

"List all public channels in my Flock workspace"

03

"Get the metadata for user '@john_doe'"

Troubleshooting Flock MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Flock + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Flock to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.