Bring Contact Management
to VS Code Copilot
Learn how to connect Polaria 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 Polaria MCP Server?
Transform your customer support operations by connecting Polaria directly to your AI agent. Let your assistant automatically retrieve relevant help articles, instantly respond to customer conversations, and efficiently manage your user directory without navigating away from your central workspace.
What you can do
- Access and organize your entire customer contact database
- Read and respond to live chat conversations instantly
- Update the status of support tickets (Open, Pending, Resolved)
- Retrieve FAQ articles to resolve customer inquiries faster
- Manage custom attributes for targeted support
How it works
1. Log into your Polaria dashboard 2. Create a new app under Settings > Marketplace to get your Secret Key 3. Connect via Vinkius to unleash AI-powered conversational supportWho is it for?
Ideal for customer success teams, support agents, and community managers who want to resolve user queries faster and automate repetitive chat tasks.Built-in capabilities (8)
Add a message to a conversation
Create a new contact in Polaria
Get details of a specific contact
Get details of a specific conversation
List contacts in Polaria
List conversations in Polaria
List FAQs in Polaria
List Polaria widgets
Why VS Code Copilot?
GitHub Copilot Agent mode brings Polaria 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
Polaria in VS Code Copilot
Polaria and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Polaria 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 Polaria in VS Code Copilot
The Polaria 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
Polaria for VS Code Copilot
Every tool call from VS Code Copilot to the Polaria MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Where do I find my Secret Key?
Log in to Polaria, go to Settings > Marketplace > Create my own app, create a new application, and show the 'Secret Key' in the authorized applications section.
What is the Base URL for the API?
The Polaria REST API v2 base URL is: https://polaria.ai/rest/v2/
Can I modify existing conversations?
Yes, you can add replies and change the status of existing conversations directly using the Polaria MCP.
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.