The Refine MCP server
Refine AI tracks how your brand shows up in AI search engines. The Refine MCP server hands that data — and the controls behind it — straight to your AI assistant. Ask Claude how your visibility moved this week, have it draft a blog post from your top prompt, or let it manage the competitors you benchmark against. All without leaving the chat.
New to MCP?
The Model Context Protocol is an open standard that lets AI assistants securely connect to external tools and data. Refine exposes a remote MCP server, so any MCP-compatible client can talk to your Refine workspace once you give it an API key.Quickstart
Connect Refine to Claude or Cursor in under five minutes.
Tools reference
All 15 tools, with parameters and return shapes.
What you can do
The server exposes 15 tools across 5 areas:
Read your visibility
Pull mention rate, average rank and per-day history across ChatGPT, Gemini, Perplexity and more.
Manage prompts
Create, edit and remove the search prompts Refine monitors for your brand.
Track competitors
Add and benchmark competitors, and see how their AI visibility stacks up against yours.
Generate content
Spin up blog articles, Reddit responses and LinkedIn posts grounded in your prompts.
Organize with tags
Group and color-code prompts so your assistant can reason about themes.
Plug into any client
A standard Streamable HTTP MCP server — works with Claude, Cursor and the rest.
How it works
The server speaks the Streamable HTTP MCP transport. Your client opens a connection to a single endpoint and authenticates with a personal API key sent as a bearer token:
You generate an API key tied to one brand in your Refine workspace.
Your client connects to https://app.refine-app.com/api/mcp/mcp with Authorization: Bearer rfn_live_….
Every tool call is automatically scoped to that brand — no way to reach another workspace’s data.
You’ll need a paid plan
MCP tools are gated by subscription. Analytics, prompts, tags and competitors require the Visibility plan; content generation requires the Autopilot plan. See Authentication for details.