Bring Community Feedback
to VS Code Copilot
Learn how to connect UserEcho to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the UserEcho MCP Server?
Connect your UserEcho account to any AI agent and simplify how you manage your community feedback, helpdesk tickets, and self-service content through natural conversation.
What you can do
- Helpdesk Management — List all support tickets and retrieve detailed conversation history and status for specific issues.
- Direct Ticketing — Programmatically create new support tickets directly from your agent to accelerate customer assistance.
- Knowledge Base Access — List and query all articles in your help center to verify self-service documentation.
- Forum Oversight — List and monitor feedback and support forums to understand community trends and suggestions.
- User Directory — List account users and team members to manage your support organization structure.
- Issue Tracking — Monitor the progress of client requests and verify resolution times via AI.
How it works
1. Subscribe to this server
2. Enter your UserEcho API Token and Subdomain (found in your developer settings)
3. Start managing your community feedback from Claude, Cursor, or any MCP client
Who is this for?
- Customer Support Managers — quickly retrieve ticket histories and monitor team activity via simple AI commands.
- Community Managers — monitor forum feedback and verify article availability directly from the workspace.
- Product Teams — coordinate bug reports and feature requests coming from UserEcho forums.
Built-in capabilities (6)
Add a new ticket
Get details for a specific ticket
List account users
List UserEcho forums
List knowledge base articles
List helpdesk tickets
Why VS Code Copilot?
GitHub Copilot Agent mode brings UserEcho 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.
- —
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
UserEcho in VS Code Copilot
UserEcho and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect UserEcho 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 UserEcho in VS Code Copilot
The UserEcho 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 6 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
UserEcho for VS Code Copilot
Every tool call from VS Code Copilot to the UserEcho MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the full conversation history of a support ticket?
Yes! Use the get_ticket_details tool and provide the Ticket ID. Your agent will retrieve the complete metadata and all conversation threads for that specific issue.
How do I list all the help center articles in my account?
Run the list_kb_articles query. The agent will retrieve a complete list of all articles currently published in your UserEcho knowledge base.
Is it possible to create a new ticket via AI for a customer?
Absolutely. Use the create_support_ticket action. Provide a header and the detailed content, and the agent will instantly log the request in your UserEcho helpdesk.
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.