Bring Ai Assistant
to VS Code Copilot
Learn how to connect Chatsistant to VS Code Copilot and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Chatsistant MCP Server?
Connect your Chatsistant account to any AI agent and manage your AI chatbot ecosystem through natural conversation.
What you can do
- Bot Management — List all configured chatbots and inspect individual bot profiles with knowledge base settings and status
- Conversation Review — Browse all chat sessions across bots and inspect full message histories for any conversation
- Knowledge Training — Review all data sources (URLs, text, files) training a bot and add new sources programmatically
- Live Querying — Send questions to any bot and receive AI-generated answers based on its trained knowledge base
- Webhook Monitoring — View all configured webhooks with event triggers and delivery settings
How it works
1. Subscribe to this server
2. Enter your Chatsistant API Key from your dashboard settings
3. Start managing your chatbots from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Customer Experience Teams — review bot conversations, identify knowledge gaps, and improve response quality
- Developers — manage bot configurations and data sources through conversational AI instead of the dashboard
- Operations Teams — monitor webhook delivery and verify bot connectivity across all integrations
Built-in capabilities (8)
Add a new data source to a bot
Get details for a specific bot
Get details for a specific conversation
List Chatsistant bots
Optionally filter by bot ID. List bot conversations
List bot data sources
List configured webhooks
Query a bot knowledge base
Why VS Code Copilot?
GitHub Copilot Agent mode brings Chatsistant data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Chatsistant in VS Code Copilot
Chatsistant and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Chatsistant to VS Code Copilot 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 Chatsistant in VS Code Copilot
The Chatsistant 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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
Chatsistant for VS Code Copilot
Every tool call from VS Code Copilot to the Chatsistant MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send a question to a bot and get an AI-generated answer in real time?
Yes! The query_bot tool accepts a Bot ID and a question string. It sends the query to the bot's AI engine and returns a response generated from its trained knowledge base — perfect for testing bot accuracy before deploying changes.
Can I review all the data sources currently training my bot?
Yes. The list_data_sources tool returns all URLs, documents, and text snippets that have been added to a specific bot's knowledge base, including their processing status. Use add_data_source to programmatically add new URLs, text, or file content to expand the bot's training data.
Can I browse conversation histories across all my bots?
Yes. Use list_conversations to retrieve all chat sessions — optionally filter by a specific Bot ID. Then use get_conversation with the Conversation ID to inspect the full message timeline, including user questions, bot responses, and timestamps.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.