BotGenuity MCP Server for VS Code CopilotGive VS Code Copilot instant access to 6 tools to Chat With Bot, Get Chatbot Details, Get Conversation History, and more
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.
Ask AI about this App Connector for VS Code Copilot
The BotGenuity app connector for VS Code Copilot is a standout in the Customer Support category — giving your AI agent 6 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install BotGenuity and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"botgenuity": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 BotGenuity MCP Server
Connect your BotGenuity account to any AI agent and take full control of your automated customer engagement and chatbot operations through natural conversation.
GitHub Copilot Agent mode brings BotGenuity data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Bot Orchestration — List and manage all your AI chatbot instances programmatically, retrieving detailed configuration and high-fidelity operational status in real-time
- Lead Capture Intelligence — Access complete directories of leads captured during bot interactions, including high-fidelity contact metadata and conversation context
- Conversation Discovery — Retrieve detailed chat histories and individual message threads to maintain a perfectly coordinated overview of customer needs
- Real-Time Interaction — Programmatically send messages to your chatbots to test performance or integrate bot responses into custom business workflows
- Platform Monitoring — Access chatbot configuration details and monitor account-level connectivity directly through your agent for instant reporting
The BotGenuity MCP Server exposes 6 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.
All 6 BotGenuity tools available for VS Code Copilot
When VS Code Copilot connects to BotGenuity through Vinkius, your AI agent gets direct access to every tool listed below — spanning chatbot-builder, conversational-ai, digital-assistant, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Send a message to a chatbot and get a response
Get details of a specific chatbot
Get full history for a conversation
List leads captured by a chatbot
List conversations for a chatbot
List all chatbots in your BotGenuity account
Connect BotGenuity to VS Code Copilot via MCP
Follow these steps to wire BotGenuity into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using BotGenuity
Why Use VS Code Copilot with the BotGenuity MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with BotGenuity 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
BotGenuity + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the BotGenuity 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
Example Prompts for BotGenuity in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with BotGenuity immediately.
"List all my chatbots in BotGenuity."
"Show the captured leads for chatbot ID 'B123'."
"Ask my 'Customer Hero' bot: 'What are our shipping rates?'."
Troubleshooting BotGenuity MCP Server with VS Code Copilot
Common issues when connecting BotGenuity to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
BotGenuity + VS Code Copilot FAQ
Common questions about integrating BotGenuity MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.