Refine Docs

MCP server

Tools reference

The Refine MCP server exposes 31 tools. In practice you won’t call them by hand — your assistant picks the right tool from these descriptions. Click any tool to see its parameters and what it returns.

How results come back

Every tool returns its payload as JSON inside the MCP content array (a single text item holding a JSON string). Your client parses this automatically — the shapes below describe the decoded JSON.

Example call

tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_visibility",
    "arguments": { "days": "30" }
  }
}

Example result

result
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      { "type": "text", "text": "{\"mention_rate\":0.42,\"average_rank\":3.1,…}" }
    ]
  }
}

All calls go to https://app.refine-app.com/api/mcp/mcp with your bearer token.

Visibility analytics

Read-only insight into how ChatGPT, Gemini and Perplexity answer your buyers’ prompts. Any paid plan.

Opportunities & citations

Where to act next: the prompts losing the most demand, the prompts you do not track yet, and the pages AI engines cite instead of you. Any paid plan.

Content generation

Generate articles, Reddit replies and LinkedIn posts from your prompts. Autopilot plan.

Publishing to a CMS

Send a finished blog article to the WordPress or Webflow site connected in Settings. Autopilot plan.

Agent publishing loop

The three calls an autonomous agent (Hermes, Claude Code on a schedule…) needs to keep a blog alive on its own, with the cadence enforced server-side. Autopilot plan.

Prompts

Create, edit and remove the search prompts Refine monitors for your brand. Any paid plan.

Tags

Organize prompts with color-coded tags. Any paid plan.

Competitors

Track the competitors you want to benchmark against. Any paid plan.

Search Console & Analytics

Read the Google properties the customer connected in Settings, to tie AI visibility to the traffic it produces. Any paid plan.