Bring Visual Feedback
to VS Code Copilot
Learn how to connect WebVizio to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the WebVizio MCP Server?
Connect your WebVizio account to any AI agent and streamline your visual collaboration and website review processes through natural conversation.
What you can do
- Project Management — List all websites under monitoring and create new feedback projects by URL.
- Task Control — Create, list, and update feedback tasks (bugs, UI improvements) directly on specific projects.
- Visual Discussion — List and add comments to tasks to keep the review conversation organized.
- Integration Monitoring — List configured webhooks to ensure your event-driven workflows are active.
- Technical Insights — Retrieve detailed logs and metadata for individual tasks and project URLs.
How it works
1. Subscribe to this server
2. Enter your WebVizio API Token (found in your account profile or settings)
3. Start reviewing and managing your websites from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Web Designers & QA Teams — quickly log visual bugs and track UI improvement tasks via simple AI queries.
- Project Managers — monitor feedback progress across multiple website projects without leaving the workspace.
- Agencies & Clients — coordinate website reviews and discussion threads directly from the AI assistant.
Built-in capabilities (10)
Add a comment to a task
Create a new project
Create a new feedback task
Get project details
Get task details
List comments on a task
List all website feedback projects
List tasks in a project
List configured webhooks
Update a task status or details
Why VS Code Copilot?
GitHub Copilot Agent mode brings WebVizio data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
WebVizio in VS Code Copilot
WebVizio and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect WebVizio 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 WebVizio in VS Code Copilot
The WebVizio 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 10 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
WebVizio for VS Code Copilot
Every tool call from VS Code Copilot to the WebVizio MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create a new project using just a URL?
Yes! Use the create_webvizio_project tool and provide the website URL. Your agent will add it to your WebVizio dashboard for monitoring.
How do I see all the bugs reported for a specific site?
Run the list_webvizio_tasks query with your Project ID. It will return a complete list of all feedback tasks, including status and descriptions.
Is it possible to reply to feedback comments via AI?
Absolutely. Use the add_webvizio_comment tool by providing the Task ID and your text to post a new comment to the visual discussion thread.
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.