4,500+ servers built on MCP Fusion
Vinkius
Userback logo
Vinkius
Claude Code logo

How to Use the Userback MCP in Claude Code

Automate Userback data harvesting for CI/CD pipelines using Claude Code's terminal execution.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Userback MCP on Cursor AI Code Editor MCP Client Userback MCP on Claude Desktop App MCP Integration Userback MCP on OpenAI Agents SDK MCP Compatible Userback MCP on Visual Studio Code MCP Extension Client Userback MCP on GitHub Copilot AI Agent MCP Integration Userback MCP on Google Gemini AI MCP Integration Userback MCP on Lovable AI Development MCP Client Userback MCP on Mistral AI Agents MCP Compatible Userback MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Code

Connect Userback MCP to Claude Code

Create your Vinkius account to connect Userback to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Retrieve Project Metadata via Claude Code MCP Server

Run `get_project_details` in a pipeline to fetch the full metadata of a Userback project. This allows your script to validate deployment requirements or check feature flags before release. Instead of manually checking the UI, you pipe this structured JSON output directly into your build log or database.

Index and Filter Userback Feedback in Scripts

Use `list_feedbacks` to pull a machine-readable list of all bug reports. This is essential for automated reporting—you can count how many open issues exist across your entire product line. Your shell script processes this output, sending metrics directly to Slack or Jira without needing manual intervention.

Audit User Account Lists from the Terminal

Execute `list_account_users` when running setup scripts. This confirms that all required user roles are provisioned and accessible for testing purposes. It provides a definitive list of active accounts, letting your CI/CD job know exactly which credentials to assume during deployment.

Setup guide

Set up Userback MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see userback-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest Userback transactions." It will automatically discover and invoke the available Userback tools.

Terminal
claude mcp add --transport http userback-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Userback MCP in Claude Code

You run `get_project_details` directly in your script. The tool returns the necessary metadata, allowing you to write conditional logic: if the project is active, proceed; otherwise, fail the build.
The server handles structured bug reports and annotations. You get text descriptions, IDs, and metadata associated with screenshots or recordings when calling `get_feedback_details`.
Yes. Running `list_feedbacks` streams the entire list of entries to standard output. You can then pipe this through grep or awk to filter by date range or severity.
The server exposes basic user identifiers and names via `list_account_users`. It only provides enough context for auditing purposes; it doesn't provide private credentials.
The server touches project metadata and user accounts. Specifically, the `list_userback_projects` tool retrieves names and IDs used for auditing.

Start using the Userback MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for Userback. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.