MCP Server

Give your AI agent the facts about your published content. Before it edits or republishes a post, it can ask LiquiChart which numbers went stale and what the proposed fix is, then approve it or start watching a new page.

Connect

Requires an active Pro or Team plan. The server speaks Streamable HTTP at https://www.liquichart.com/api/mcp.

Claude Code

Create an API key in Settings > API with the claims, monitored pages, living content and workspace scopes.

claude mcp add --transport http liquichart https://www.liquichart.com/api/mcp \
  --header "x-api-key: lc_live_..."

Claude, Cursor and Other OAuth Clients

Add https://www.liquichart.com/api/mcp as a custom connector. You will be asked to sign in to LiquiChart and approve access for the current workspace. No API key is needed, and you can revoke access any time in Settings.

Clients That Send Only a Bearer Token

{
  "mcpServers": {
    "liquichart": {
      "url": "https://www.liquichart.com/api/mcp",
      "headers": { "Authorization": "Bearer lc_live_..." }
    }
  }
}

Tools

Tool	What It Does
get_overview	Claim counts by status, corrections waiting for review, and the plan.
list_stale_claims	Claims whose data changed or that need review, with what changed. Filter by page.
list_monitored_pages	Pages LiquiChart is watching, with claim counts and last check.
get_monitored_page	One monitored page: claim and stale-claim counts, fetch errors.
list_corrections	Proposed corrections: current text, recommended text and reason.
get_correction	Full detail of one correction.
watch_pageMakes changes	Start monitoring a URL. Reads the page and tracks its claims right away.
approve_correctionMakes changes	Approve a correction, optionally edited. On Team, can publish to a CMS-connected page.
reject_correctionMakes changes	Remove a correction from the review queue.

Limits and Permissions

Every tool call runs through the REST API, so the same rules apply: your key's scopes, its IP allowlist, your plan's monitored-page limit, and the API rate limits. Approving a correction on a page without a CMS connection does not change the live page; apply the returned text and LiquiChart confirms it on the next scan.