Integration

changes.page integration

changes.page hosts product changelog pages. Read the public posts of one changelog page: the latest post, the pinned post, the 50 most recent posts, or one post by id, each with its title, Markdown content, tags, dates and public link. Useful to relay a product's new release notes to another channel. Creating, editing and deleting posts (done with the page's secret key through the changes.page CLI) is not exposed. No API key is needed: the connection only holds the page's subdomain.

Connect changes.page How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in changes.page.Built from the 4 changes.page tools below, on the connection you add once.

What you can do with changes.page

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Change, 2 operations

get_postGet postGETReturns one post of the changelog page by its id: title, Markdown and plain-text content, tags, dates and public link. An unknown id answers 404.
list_postsList postsGETLists the posts of the changelog page, newest first, at most 50: id, title, Markdown and plain-text content, tags, publication, creation and update dates, and each post's public link.

Latest, 1 operation

get_latest_postGet latest postGETReturns the most recent post of the changelog page (it may be the pinned post): id, title, Markdown content, tags, publication, creation and update dates, and the post's public link.

Pinned, 1 operation

get_pinned_postGet pinned postGETReturns the pinned post of the changelog page: id, title, Markdown content, tags, dates and public link. When no post is pinned the page answers 404 with null, so the call fails.

Use changes.page from Claude Code, Cursor or Codex

Connect changes.page in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its changes.page operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect changes.page

Create your workspace
Sign up free. Nothing to install.
Connect changes.page once
Add your changes.page connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.