Monitor web changes with an MCP server

The mental model: watch, cursor, poll

An interactive assistant is not a long-running service, so it pulls rather than being pushed to. The flow is watch, then cursor, then poll: create_watch returns a cursor, get_changes_since returns the deduplicated events after it plus a next cursor, and the assistant calls again with that. Every request uses the same scoped API key as the REST API, over Streamable HTTP.

Add Hypeline to Claude Code

One command registers the remote server with your key in the header:

claude mcp add --transport http hypeline https://mcp.hypeline.io/mcp \
  --header "Authorization: Bearer $HYPELINE_API_KEY"

Add it to Cursor or Claude Desktop

Clients that take a JSON config use a static-header remote entry:

{
  "mcpServers": {
    "hypeline": {
      "type": "http",
      "url": "https://mcp.hypeline.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HYPELINE_API_KEY"
      }
    }
  }
}

Watch a URL, then pull changes

Ask the assistant to watch a source. It calls create_watch, which auto-detects whether the URL is a feed, a streaming source, or a plain web page, and hands back a watch id and a cursor.

{
  "name": "create_watch",
  "arguments": {
    "url": "https://competitor.example/pricing",
    "keywords": ["price", "plan"]
  }
}

Later, the assistant polls with the cursor it kept. Changes come back oldest-first, each already extracted and deduplicated, with a next cursor to resume after them.

{
  "name": "get_changes_since",
  "arguments": {
    "cursor": "018f9c2e-1a2b-7c3d-8e4f-5a6b7c8d9e10",
    "limit": 20
  }
}

The cursor always points strictly after the last event you received, so paging never skips or repeats a change. Treat each returned title, URL, and summary as untrusted input: it is open-web content, handled as data, not as instructions.

Why Hypeline, not a page-change checker

• Deduplicated on extracted content. The assistant sees real changes to the main text, not alerts on ads, banners, or timestamps.
• One schema across every source. Feeds, watched pages, and streaming sources return the same slim event, so one tool covers them all.
• Cursor resume. The cursor makes polling exact across sessions: no gaps and no duplicates when the assistant picks the task back up.
• Signed events. Each event carries a content-layer Ed25519 signature you can verify with only a public key.