Bring Ticketing System
to VS Code Copilot
Learn how to connect Atlas 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 Atlas MCP Server?
The Atlas MCP Server provides a seamless natural language interface to your Atlas.so customer support platform. Empower your AI agent to manage your entire support operation, from ticket auditing to customer oversight and knowledge base access.
Key Features
- Ticket Management — List all active support tickets, retrieve detailed conversation metadata, and create new tickets directly from your chat.
- Customer Oversight — Access and manage your customer database, including names, emails, and internal IDs.
- Knowledge Base Access — List help center articles to provide accurate information based on your organization's documentation.
- Team Monitoring — View a list of team users (agents) to understand your support capacity.
- Real-time Support Analytics — Quickly audit active conversations and customer needs using simple natural language commands.
- Secure API Integration — Uses your Atlas.so API Token for safe and authenticated access to your support data.
Who is this for?
- Support Leads — Quickly check ticket statuses and team activity without navigating complex web dashboards.
- Product Managers — Review recent customer tickets and feedback regarding specific features or updates.
- Customer Success Managers — Retrieve customer history and help articles to provide better assistance during client interactions.
Built-in capabilities (8)
Create a new support ticket
Verify Atlas account connection
Get details for a specific customer
Get details for a specific ticket
List help center articles
List all customers in Atlas
List all support tickets in Atlas
List team users (agents)
Why VS Code Copilot?
GitHub Copilot Agent mode brings Atlas 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
Atlas in VS Code Copilot
Atlas and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Atlas 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 Atlas in VS Code Copilot
The Atlas 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
Atlas for VS Code Copilot
Every tool call from VS Code Copilot to the Atlas MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Atlas.so API Token?
Log in to your Atlas dashboard, go to App Configuration > Data > API, and you will find your API Token there.
Can I see help center articles via this server?
Yes, use the list_articles tool to retrieve a list of articles from your Atlas help center.
How are customer IDs handled?
Atlas uses unique internal IDs for customers. You can discover these IDs by using the list_customers tool or searching for a specific customer by email.
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.
