Refix
Server Details
Refix is an AI analyst for company data. Ask business questions, analyze connected sources, set up watchers on ongoing goals, and catch up on findings from your AI assistant. Requires a Refix account and connected data sources. Connect with OAuth.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- Refix
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: the investigation lifecycle (investigate/get/cancel), watcher CRUD, and findings listing are well separated. The only mild overlap is refix_get_context vs refix_get_profile (both read workspace/user setup info) and refix_investigate being overloaded to start, answer clarifications, and dig into findings, though its description disambiguates the modes explicitly.
All tools share the refix_ prefix and follow a verb_noun pattern (get_watcher, create_watcher, list_findings, cancel_investigation). The one deviation is refix_investigate, a bare verb with no noun, but it is still predictable given the refix_ namespace.
Ten tools is well within the sweet spot and each maps to a real operation: three investigation lifecycle tools, four watcher tools, findings listing, and two read-only context tools. No tool appears redundant or filler.
Coverage is strong: investigations can be started, polled, answered, and cancelled; watchers can be created, listed, read, paused/resumed/stopped, and have alert destinations amended; findings can be listed and drilled into via finding_id. Minor gaps exist in that watchers cannot be deleted (only stopped/amended) and there is no way to fetch a single finding directly or list investigation history.
Publisher details
- Operator
- Refix · Publisher source
- Operator website
- Unknown
- Vendor relationship
- Unknown
- Documentation
- Unknown
- Privacy policy
- Not provided
- Trust center
- Unknown
- Restrictions
- Unknown
Available Tools
10 toolsrefix_cancel_investigationCancel investigationBDestructiveIdempotentInspect
Request cancellation of a running investigation. Safe to call more than once.
Inputs: idempotency_key (required), investigation_id (required). Returns: state, investigation_id
refix_create_watcherCreate watcherAIdempotentInspect
Call refix_list_watchers first and do not create a duplicate. Create a Refix watcher. A watcher carries a goal: Refix keeps working on it against the workspace's connected data and reports what it finds to the chosen place. Use it for ongoing goals, not one-off questions. Tell the user that watchers count toward the workspace's Refix usage and that everyone in the workspace can see them. alerts: 'mcp_assistant' keeps alerts in Refix for you to read with refix_list_findings (no Slack post, no email); 'slack' or 'email' must match alert_channel from refix_get_context.
Inputs: alerts (required), timezone (required), objective (required), idempotency_key (required). Returns: title, alerts, status, objective, +5 more
refix_get_contextGet contextARead-onlyIdempotentInspect
Read workspace readiness and setup links. Does not start analysis.
Inputs: no named parameters. Returns: links, ready, workspace, capabilities, +4 more
refix_get_investigationGet investigationARead-onlyIdempotentInspect
Read the state of an investigation started with refix_investigate. While it is queued or running, this call waits up to 25 seconds for the state to change or for a new step in progress, so call it again right away until it finishes. The user sees nothing while this runs unless you send it: when a result has new_steps, tell the user in one short plain sentence what Refix is doing before the next call. Use Refix's numbers exactly. Never starts or reruns analysis. When the state is needs_input, ask the user pending_input.question and send their answer with refix_investigate and response_to_input_id. When the answer ends with suggested follow-ups, offer them to the user; send the one they pick with refix_investigate and this session_id.
Inputs: investigation_id (required). Returns: state, answer, question, new_steps, +6 more
refix_get_profileGet profileARead-onlyIdempotentInspect
Return the Refix profile behind this connection: the signed-in user and their workspace. The opaque id stays the same across token refresh and reconnects. Does not start analysis.
Inputs: no named parameters. Returns: id, name, email, nickname
refix_get_watcherGet watcherARead-onlyIdempotentInspect
Read one watcher's status, alert destination, and its most recent checks.
Inputs: watcher_id (required). Returns: title, alerts, status, objective, +6 more
refix_investigateInvestigateAIdempotentInspect
Start a new Refix investigation, or answer a pending clarification with response_to_input_id, or dig into a finding from refix_list_findings with finding_id. Send at most one of session_id, response_to_input_id or finding_id. Counts toward the workspace's Refix usage. For a follow-up about an earlier Refix answer in this chat, pass that answer's session_id so Refix keeps the context. If the question names a tool that is not in usable_sources from refix_get_context, tell the user it is not connected and ask whether to check the connected sources before starting. Give the user report_url at once: it opens this conversation in Refix. Then call refix_get_investigation for the result; do not start another investigation to check progress.
Inputs: question (required), idempotency_key (required), finding_id, session_id, +1 more. Returns: state, report_url, session_id, investigation_id
refix_list_findingsList findingsARead-onlyIdempotentInspect
Read the proactive updates Refix sent this user (watcher alerts, updates Refix sends on its own, reminders), newest first, from the last 7 days by default. Pass since, such as the time of your last check, to get only newer updates. Reads change nothing here (no read receipts, no resolutions). Say 'nothing new' only when this call succeeds with no items.
Inputs: limit, since, watcher_id. Returns: items, has_more
refix_list_watchersList watchersBRead-onlyIdempotentInspect
List this workspace's watchers, as the dashboard does. Every workspace member sees every watcher.
Inputs: limit, cursor, status. Returns: watchers, next_cursor
refix_update_watcherUpdate watcherADestructiveIdempotentInspect
Pause, resume or stop a watcher, or amend where its alerts go. The objective cannot change; create a new watcher instead. Any workspace member can change any watcher, matching the dashboard.
Inputs: action (required), watcher_id (required), idempotency_key (required), alerts. Returns: title, alerts, status, objective, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.