Skip to content
AdsChatGPT now shows ads.Get early access
Integrations

Everything Refine connects to.

The engines it listens to, the data it reads, the sites it publishes to, and the assistants it works inside. Everything here is live today, with the plan it needs marked next to it. Copilot and Mistral are read on request. What ships next lands on the changelog.

Engines7

  • ChatGPT
  • Gemini
  • Perplexity
  • ClaudeAutopilot
  • AI OverviewsAutopilot
  • CopilotOn request
  • MistralOn request

Your data3

  • Search Console
  • GA4
  • AI traffic

Publishing4

  • WordPress
  • Webflow
  • Shopify
  • Next.js

Assistants4

  • Claude
  • Cursor
  • ChatGPT
  • Any MCP

Listening

The engines we monitor

Every day, Refine asks each engine the questions your buyers ask, in the product itself rather than through its API, and records the answer: whether you are named, where, in what tone, and from which sources.

  • ChatGPT

    Including sponsored placements when they appear in the answer.

  • Google Gemini

    The closest proxy for what AI Overviews will surface.

  • Perplexity

    Cites its sources most explicitly. The clearest read on who gets cited.

  • Claude

    Anthropic’s assistant, read on Autopilot and Scale.

    Autopilot

  • Google AI Overviews

    The answer block at the top of Google results, read on Autopilot and Scale.

    Autopilot

  • Microsoft Copilot

    The assistant inside Windows, Edge and Microsoft 365.

    On request

  • Mistral

    Le Chat, for the markets where it holds share.

    On request

Your own numbers

Your data, next to theirs

Visibility numbers say where you are absent; your own traffic says which absences cost you. Connecting both turns a report into a to-do list.

  • Google Search Console

    The topics you rank for but are not cited on, and the reverse. Read access only.

    Autopilot

  • Google Analytics 4

    Sessions and conversions by page, next to the answers that cite it.

    Autopilot

  • AI traffic snippet

    A 1 KB script that attributes each visit to the assistant it came from.

    Autopilot

Publishing

From draft to live, on your domain

The agents write the article, and it goes live on your site as server-rendered HTML. The kind AI crawlers, which do not run JavaScript, can read and cite.

  • WordPress

    Draft or live post, in the category you choose.

  • Webflow

    To the CMS collection of your choice.

  • Shopify

    To the blog of your store, next to the products it should sell.

  • Next.js

    A pull request on GitHub, or @getrefine/next: one file of setup, no rebuild.

    npm

MCP Server

Inside the assistant you already use

Refine ships its own MCP server. Your assistant reads your visibility, manages your prompts, and writes and publishes content, from the conversation you are already in.

Terminal
claude mcp add --transport http refine \
  https://app.refine-app.com/api/mcp/mcp \
  --header "Authorization: Bearer rfn_live_your_key"
Read the docs

  • Claude Desktop & Claude Code

    One-click connect from the app, or one command in the terminal.

  • Cursor

    The same server, for teams that live in their editor.

  • Meta Muse

    Ask Muse to build a custom connector from the server. Setup on the Muse page.

    Setup

  • ChatGPT

    Connect Refine as a tool and ask ChatGPT how you are doing in ChatGPT.

  • Any MCP client

    Streamable HTTP with a personal API key.

Something missing?

HubSpot, Notion, a CMS we have not listed: tell us what you publish with and what you measure with, and we will say honestly whether it is weeks or quarters away. The credentials you hand us are encrypted before storage: the details are on the security page.