Bring Visual Feedback
to VS Code Copilot
Learn how to connect Userback 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 Userback MCP Server?
Connect your Userback account to any AI agent and simplify how you collect and manage visual feedback, bug reports, and user suggestions through natural conversation.
What you can do
- Feedback Management — List all feedback entries and retrieve detailed metadata, screenshots, and comments for specific reports.
- Project Control — List and query feedback projects to keep your development and design work organized.
- Direct Creation — Programmatically create new feedback entries or bug reports for specific projects via AI.
- Team Visibility — List account users and collaborators to understand your organization's review team.
- Status Tracking — Monitor the progress of feedback items and verify if issues have been resolved.
How it works
1. Subscribe to this server
2. Enter your Userback API Token (found in your account settings under API)
3. Start managing your visual feedback from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers & Designers — quickly retrieve user feedback and verify visual bugs via simple AI commands.
- QA & Support Teams — monitor incoming reports and create feedback entries directly from the workspace.
- Development Leads — coordinate bug fixes and track feedback status across multiple projects.
Built-in capabilities (6)
Create a new feedback entry
Get details for a specific feedback
Get details for a specific project
List account users
List Userback feedbacks
List Userback projects
Why VS Code Copilot?
GitHub Copilot Agent mode brings Userback 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
Userback in VS Code Copilot
Userback and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Userback 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 Userback in VS Code Copilot
The Userback 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
Userback for VS Code Copilot
Every tool call from VS Code Copilot to the Userback MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I filter feedback by project ID?
Yes! Use the list_feedbacks tool and provide the optional project_id parameter to retrieve entries only for that specific project.
How do I see the comments on a specific feedback item?
Run the get_feedback_details query with the unique Feedback ID. Your agent will retrieve the complete metadata, including any internal or user comments.
Is it possible to create a new bug report via AI?
Absolutely. Use the create_feedback_entry action. Provide the Project ID, a title, and an optional comment to log a new entry in your Userback account.
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.