Refiner
Refiner is a customer feedback and survey tool designed to help businesses collect and analyze user insights.
Verdict
Common use cases
- Pull NPS scores during product review meetings
- Filter contacts by segment for outreach planning
- Audit active surveys before launching new campaigns
- Retrieve response data for customer success reports
- Check account usage before upgrading plan
Integration
- Vendor
- Refiner
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
refiner
Tools
- Delete Contactdestructive
Tool to delete a specific contact by its identifier. use after confirming the contact's id, email, or uuid.
- Get Account Info
Tool to fetch refiner account subscription and environment usage details. use when you need to audit your current plan and usage.
- Get Contact
Tool to retrieve details of a specific contact by its id. use when you need all stored traits for a known user.
- Get Contacts
Tool to retrieve a list of contacts from your refiner account. use when you need to filter or paginate through contacts.
- Get Forms
Tool to retrieve a list of forms (surveys) from your refiner account with optional filtering and pagination. use when you need to list surveys by state, page, or include extra info/config.
- Get Reporting
Tool to retrieve aggregated reporting data for surveys including metrics and analytics. use when you need survey analytics over a time range filtered by type, question identifiers, tags, forms, or segments.
- Get Segments
Tool to retrieve a list of user segments from your refiner account. use when you need to view or paginate segments.
- Get Survey Responses
Tool to retrieve all survey responses from your refiner account with optional filtering and pagination. use after confirming survey creation to pull response data.
- Track Event
Tool to record a user event by name for a user identified via user id or email. use after confirming the identifier and event name.
- Update Contact
Tool to update an existing contact's attributes or account. use when you have a contact `id` or `email` and want to modify traits or grouping.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Refiner in the MCP directory and click Connect. 3. You'll be prompted for an API key — log into your Refiner account, go to Settings > API, and generate a new key with read/write access. 4. Paste the key into Switchy and click Authorize. 5. Return to any Space and type '@Refiner get account info' to confirm the connection works. 6. If the tool returns your subscription details, you're set. 7. To invoke a tool, @mention Refiner in a message and describe what you need — for example, '@Refiner show me NPS responses from the last 30 days' or '@Refiner list all contacts in the trial segment'. 8. The AI will map your request to the appropriate tool and return structured data you can discuss or export.
What teammates see: by default, memories from Refiner are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
NPS Trend Summary
@Refiner get survey responses for our NPS form from the last 90 days, then summarize the score trend and flag any detractor comments that mention pricing or support.Open in a Space →
Segment Contact List
@Refiner list all contacts in the 'Enterprise Trial' segment and show me their email addresses and signup dates.Open in a Space →
Active Survey Audit
@Refiner show me all active surveys, include response counts and creation dates, then highlight any that have fewer than 10 responses.Open in a Space →
Account Usage Check
@Refiner get my account info and tell me how many survey responses I have left this month and whether I'm close to any limits.Open in a Space →
Response Deep Dive
@Refiner retrieve all responses for the 'Feature Request Survey' from the last 60 days and summarize the most common feature requests mentioned in open text fields.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Refiner show me all active surveys and their response counts from the last 30 days
Based on your Refiner account, here are the active surveys from the past 30 days: 1. **Product Satisfaction Q1 2024** (ID: frm_abc123) – 247 responses, last updated 2 days ago 2. **Feature Request Survey** (ID: frm_def456) – 89 responses, last updated 5 days ago 3. **Onboarding Feedback** (ID: frm_ghi789) – 156 responses, last updated 1 day ago All three surveys are currently live. The Product Satisfaction survey has the highest engagement rate at 34%. This example illustrates typical survey metadata; actual response counts and engagement metrics will reflect your account's real-time data.
This example combines the Get Forms and Get Reporting tools to surface survey performance. Requires read access to your Refiner API key. Response counts and metrics are aggregated server-side, so large accounts may see slight delays in real-time accuracy. Useful for weekly check-ins on survey health.
@Refiner find all contacts in the 'Enterprise Trial' segment and show me their signup dates
Found 23 contacts in the 'Enterprise Trial' segment: • sarah.chen@acme.com – signed up Jan 15, 2024 • mike.torres@techcorp.io – signed up Jan 18, 2024 • priya.kumar@startup.co – signed up Jan 22, 2024 • [20 more contacts listed with emails and signup dates] All contacts have the 'plan_type: enterprise_trial' trait. This example shows how segment membership and contact traits combine; your actual results will vary by segment definition and contact data stored in Refiner.
This example chains Get Segments with Get Contacts to filter by segment membership. Pagination applies if you have more than 100 contacts in a segment—results may require multiple API calls. Contact traits (like signup date) must already exist in Refiner; the MCP cannot infer missing data.
@Refiner delete the contact with email 'test.user@example.com' and confirm it's removed from all active segments
Contact 'test.user@example.com' (ID: cnt_xyz789) has been deleted from your Refiner account. This contact was previously a member of 2 segments: 'Beta Testers' and 'Monthly Newsletter'. Deletion is permanent and removes the contact from all segments, survey response history, and trait storage. The contact will no longer appear in reporting or receive surveys. This example demonstrates a destructive action; verify the contact identifier before running this in production.
This example uses Delete Contact, a write operation that cannot be undone. Requires API key with delete permissions. Deleting a contact also removes their survey responses from aggregated reporting, which may affect historical analytics. Always confirm the contact's identifier (email, ID, or UUID) before deletion to avoid accidental data loss.
Use-case deep-dives
When Refiner beats manual NPS triage for product teams
A 6-person product team ships a feature and sends an NPS survey to 800 users. Responses trickle in over three days. Without Refiner's MCP, someone exports a CSV daily and manually tags detractors in Notion. With the MCP, Switchy pulls survey responses every morning, flags scores under 7, and cross-references contact traits (plan tier, signup date) to prioritize who to call first. The Get Survey Responses and Get Contact tools do the heavy lifting. This works until you hit ~5,000 responses per survey—then the pagination gets slow and you're better off scheduling a nightly export. If your team runs NPS quarterly and acts on feedback within 48 hours, Refiner's MCP turns a 90-minute manual task into a 5-minute Switchy prompt.
Refiner for weekly account health checks in CS teams
A 3-person customer success team tracks 200 accounts and wants a weekly health score based on survey sentiment and usage traits. They store traits in Refiner (last login, feature adoption flags) and run a monthly CSAT survey. Every Monday, Switchy uses Get Contacts to pull the full contact list, filters by segment (Get Segments), and joins CSAT scores from Get Reporting. The output is a ranked list of at-risk accounts with context: 'Account X scored 2/5 CSAT, last login 18 days ago, trial expires Friday.' This breaks down if your contact list exceeds 10,000 records—pagination becomes a bottleneck and you'll want a data warehouse instead. For small CS teams with under 500 active accounts, Refiner's MCP is the fastest way to automate health scoring without engineering help.
When Refiner's MCP helps research teams clean segment drift
A solo UX researcher at a B2B SaaS company maintains 12 user segments in Refiner (power users, churned trials, enterprise admins). Every quarter, she audits segment definitions because traits drift—someone tagged 'enterprise' downgraded to starter, or a 'power user' hasn't logged in for 60 days. Manually clicking through Refiner's UI takes an hour. With Switchy and the MCP, she prompts: 'Show me all contacts in the power-user segment who haven't logged in this month.' Get Segments pulls the segment IDs, Get Contacts filters by trait, and she gets a CSV in 90 seconds. The limit: if you have overlapping segment logic (nested AND/OR rules), the MCP can't reconstruct the full query—you'll need to export from Refiner's UI. For straightforward segment audits under 20 segments, this MCP saves an hour every quarter.
Frequently asked
What does the Refiner MCP do in Switchy?
It connects Switchy to your Refiner survey account so AI can pull contact lists, survey responses, reporting data, and segments. You can ask questions like 'show me NPS responses from last month' or 'delete this test contact' without opening the Refiner dashboard. The MCP handles reads and writes — it can delete contacts and fetch account usage, not just view data.
Do I need admin access to connect Refiner?
You need an API key from your Refiner account settings. Refiner doesn't use OAuth — you generate a key in the dashboard and paste it into Switchy. Anyone with account-level access in Refiner can create a key, but that key inherits full account permissions. If you're on a team plan, check with your admin before connecting.
Can the Refiner MCP send new surveys or edit questions?
No. The MCP reads survey metadata and responses but doesn't create or modify surveys. You still design forms in Refiner's builder. Once a survey is live, the MCP can pull responses, filter by date or tag, and export reporting metrics. Think of it as a read-heavy analytics layer, not a survey authoring tool.
Why use this instead of exporting CSVs from Refiner?
The MCP lets you query survey data in natural language and cross-reference it with other tools in Switchy — like pulling Refiner NPS scores alongside Slack sentiment or GitHub issue counts. You skip the export-download-upload loop. For one-off reports, a CSV is fine. For recurring analysis or multi-tool workflows, the MCP saves hours per week.
Who on the team should connect the Refiner MCP?
Whoever owns customer feedback analysis — usually a product manager, researcher, or ops lead. The API key grants full account access, so don't share the connection with contractors or junior team members unless you trust them with delete permissions. On Switchy's Team plan, one person connects it and everyone queries through shared workspaces.