Bring Visual Feedback
to Claude Code
Learn how to connect Userback to Claude Code 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 Claude Code?
Claude Code registers Userback as an MCP server in a single terminal command. Once connected, Claude Code discovers all 6 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Userback data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Userback tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Userback in Claude Code
Userback and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Userback to Claude Code 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 Claude Code
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 Claude Code 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 Claude Code
Every tool call from Claude Code 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.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable