Refix MCP

Use Refix from your AI assistant.

Ask Refix to investigate a business question, pursue an ongoing goal, or catch you up on what it found, directly from Muse and other MCP clients.

M Muse
Refix connected
You asked Muse

Why did trial-to-paid conversion drop last month?

Refix Investigation complete

Trial starts held steady. The drop came after activation, where fewer new users reached the first shared report.

Evidence checked Review the finding
MCP endpoint https://mcp.refix.ai/mcp

Used by teams at

What assistants can do

Bring Refix into the conversation you already started.

Your assistant handles the conversation. Refix handles the business investigation, using the data and context already connected to your workspace.

  • Investigate a question

    Ask in your own words. Refix follows the evidence across the connected sources in your workspace.

  • Keep a goal moving

    Create and manage watchers that pursue an outcome over time and report useful findings.

  • Catch up on findings

    Read watcher alerts, reminders, and other proactive updates without starting another investigation.

Example prompts

Ask about the outcome, not the table.

Refix chooses the relevant connected sources, tests likely explanations, and returns the evidence behind its answer.

  • “Investigate why trial-to-paid conversion dropped last month.”
  • “Find the biggest revenue leak in our customer journey and recommend what to test next.”
  • “Compare retention across acquisition channels and explain what drives the difference.”
  • “Watch failed payments and tell me when a pattern needs attention.”
  • “What has Refix found about our growth goals this week?”
  • “Dig deeper into the latest Refix finding and show me the supporting evidence.”

Connect

One endpoint. Your Refix workspace.

The Model Context Protocol connection uses standard discovery and browser-based authorization. No API key is required.

Hosted MCP endpoint https://mcp.refix.ai/mcp Streamable HTTP
Authentication
OAuth 2.0 with PKCE
Client registration
Dynamic registration supported
API keys
Not supported
  1. 01

    Add the endpoint

    Use the hosted Refix MCP endpoint in Muse or another compatible assistant.

  2. 02

    Sign in to Refix

    OAuth with PKCE opens in your browser. Refix does not use API keys for this connection.

  3. 03

    Choose a workspace

    Review the requested access and approve one shared Refix workspace for the assistant.

Tools

The Refix MCP toolset.

A client should call refix_get_context before new work. It reports what the workspace can use and what needs setup.

Workspace

Check readiness, usable sources, available credits, and setup links.

  • refix_get_context

Investigations

Start a question, read its result, answer a clarification, or cancel the run.

  • refix_investigate
  • refix_get_investigation
  • refix_cancel_investigation

Watchers

Create an ongoing goal, inspect recent checks, or pause, resume, and stop it.

  • refix_create_watcher
  • refix_list_watchers
  • refix_get_watcher
  • refix_update_watcher

Findings

Read proactive updates that are visible to the connected user.

  • refix_list_findings

Access and control

The assistant gets only the workspace you approve.

Refix checks membership and consent on every request. Disconnect the assistant from your Refix settings when access should end.

What you need

  • An active Refix cloud workspace
  • Membership in the workspace you select
  • A connected source for business investigations
  • Available workspace credits for investigations and watchers

What stays controlled

  • One Refix workspace per assistant connection
  • Read-only access to connected data sources
  • Workspace-wide visibility for watchers
  • Human review for proposed actions in connected tools

Questions about Refix MCP.

Connecting an assistant and understanding what it can access.

Talk to a human

How does an assistant connect to Refix?

Add the hosted MCP endpoint. Refix uses OAuth with PKCE and dynamic client registration. You sign in, choose a workspace, and approve access in your browser.

Does the Refix MCP connection use API keys?

No. The connection uses OAuth with PKCE. Never paste Refix credentials, integration credentials, or payment details into an assistant chat.

Can the assistant change data in a connected source?

No. The MCP connection does not write directly to connected sources. A proposed action in a tool such as Linear or Jira requires a person to review it in Refix.

Which MCP requests use workspace credits?

Investigations and watchers use workspace credits. Reading workspace context and existing findings does not use credits.

Can I connect a self-hosted or dedicated Refix workspace?

Not currently. The hosted MCP endpoint is available for Refix cloud workspaces on the shared service.

Can one connection access more than one workspace?

No. One connection is approved for one workspace. Connect Refix again when you need to use a different workspace.

Bring Refix into your AI assistant.