Bring Customer Feedback
to Claude Desktop
Learn how to connect Refiner to Claude Desktop and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Refiner MCP Server?
Connect your Refiner customer feedback account to any AI agent and simplify how you collect in-product insights, manage user segments, and monitor survey performance through natural conversation.
What you can do
- Survey Oversight — List all in-app, email, and link surveys and retrieve detailed status and response counts.
- Response Analysis — Query survey submissions with technical filters like UUIDs and date ranges to identify trends.
- Identity & Targeting — Identify users and upsert technical traits to ensure surveys reach the right audience.
- Event-Driven Feedback — Track high-fidelity user actions programmatically to trigger perfectly timed micro-surveys via AI.
- Segment Intelligence — List and query defined user segments to understand your audience distribution.
- Operational Monitoring — Check API health and verify account configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Refiner API Key (found in your project settings)
3. Start managing your feedback ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers — quickly check survey results and user sentiment via simple AI commands.
- Growth & Marketing — automate event tracking and verify segment metadata directly from the workspace.
- Customer Success — monitor individual user feedback and verify identity traits via the AI assistant.
Built-in capabilities (8)
Check API Status
Get contact details
Identify or update user
List product contacts
List survey responses
List user segments
List feedback surveys
Track user event
Why Claude Desktop?
Claude Desktop is the definitive way to connect Refiner to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Refiner in Claude Desktop
Refiner and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Refiner to Claude Desktop 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 Refiner in Claude Desktop
The Refiner 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 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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
Refiner for Claude Desktop
Every tool call from Claude Desktop to the Refiner MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the responses for a specific survey via AI?
Yes! Use the list_refiner_responses tool and provide the Survey UUID. Your agent will retrieve the latest submissions, which you can then ask the AI to summarize or filter by date.
How do I identify a user and add custom traits using the agent?
Use the identify_refiner_user action. Provide the User ID or Email and a JSON string of traits (e.g., '{"plan":"pro"}'). This helps you target surveys based on specific user metadata.
Is it possible to track a custom event to trigger a survey via AI?
Absolutely. Use the track_refiner_event tool. Provide the event name and the user's ID/Email. When this event is logged, Refiner will trigger any surveys you have configured for that specific action.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.