MCP server

Endpoint

https://release-ripple-roadmap.lovable.app/mcp

Transport

Streamable HTTP (JSON-RPC over POST)

Reading

No authentication — published releases and public roadmap items only

Writing

HTTP header Authorization: Bearer lp_… with a LogPulse API key

Server name

logpulse

Server card

https://release-ripple-roadmap.lovable.app/mcp/server-card

To read changelogs, add the server with no key:

claude mcp add --transport http logpulse https://release-ripple-roadmap.lovable.app/mcp

Lovable, Claude Desktop, Windsurf and other clients take the same URL under their “custom MCP server” or “connector” setting. Clients that support discovery can read the endpoint, protocol versions, the optional API-key header and every tool's input schema from the server card (also listed in the API catalog).

Every tool returns a readable text answer plus structuredContent JSON with the same data. Tools that take a changelog use its slug — find one with search_changelogs. Drafts, scheduled releases and private roadmap items are never returned. For projects that aren't on LogPulse, convert_changelog turns their CHANGELOG.md or GitHub releases into the same shape.

Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.

{
  "query": "@acme/analytics"
}

Get a changelog's name, repository, packages, latest version and feed links.

{
  "changelog": "acme"
}

List published releases, newest first, with versions, breaking changes, migration steps and deprecations.

{
  "changelog": "acme",
  "limit": 5
}

Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.

{
  "changelog": "acme",
  "release": "2.0.0"
}

Answer “what changed between two versions, and what do I need to change?”: breaking changes with migration steps, deprecations and every release after `from` up to `to`.

{
  "changelog": "acme",
  "from": "1.4.0",
  "to": "2.0.0"
}

Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.

{
  "changelog": "acme",
  "status": "in_progress"
}

Turn any project's CHANGELOG.md text, or a GitHub release, releases page, repository or changelog file URL, into a machine-readable changelog: versions, dates, breaking changes with migration steps, and deprecations. Works for projects that aren't on LogPulse.

{
  "url": "https://github.com/vercel/next.js/releases/tag/v15.0.0"
}

publish_release and post_roadmap_update write to your own changelog, so an agent can publish the release note right after it ships. They act with a LogPulse API key that your MCP client sends as an HTTP header — set it once in the client config, from an environment variable or a password prompt. Keys are never tool arguments, so they don't end up in prompts or chat transcripts.

1. Create a key in Dashboard → Agents & API with the releases:write and/or roadmap:write permission.
2. Store it as LOGPULSE_API_KEY in your environment, then add the server with the header:

claude mcp add --transport http logpulse https://release-ripple-roadmap.lovable.app/mcp \
  --header "Authorization: Bearer $LOGPULSE_API_KEY"

Without a key, or with a key missing the permission, these tools return an error that says what to fix. Read tools keep working either way. Free plan limits apply to releases published from agents too.

Publish a release note to your own changelog right after shipping — with version, breaking changes, migration steps and deprecations. Goes live in the hosted changelog, the widget and release emails.

Needs an API key with the releases:write permission.

{
  "title": "Webhooks retry automatically",
  "version": "2.1.0",
  "category": "improved",
  "body": "Failed webhook deliveries now retry with backoff for 24 hours.",
  "deprecations": [
    {
      "item": "retry_once option",
      "replacement": "retry_policy",
      "removal_version": "3.0.0"
    }
  ]
}

Add an item to your roadmap, or update one by id — move it to in progress or shipped, change its ETA, or link the release that shipped it.

Needs an API key with the roadmap:write permission.

{
  "id": "3f0c5c1e-7b7a-4b9e-9a54-2c1d8f6a1b20",
  "status": "shipped",
  "linked_release": "2.1.0"
}

• 120 requests per minute per IP address on the MCP server, and 120 per minute per API key.
• convert_changelog also counts toward the free converter's budget: 10 conversions per minute and 100 per day per IP, shared with the REST endpoint.
• Over the limit, the server answers HTTP 429 with a Retry-After header (seconds). Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset.
• Need more for a CI pipeline or a large agent fleet? Contact us and we'll raise it.

• “Using the LogPulse changelog "acme", what changed between v1.4.0 and v2.0.0, and what do I need to change in my code?”
• “We use @acme/analytics 1.6 — is anything we rely on deprecated?”
• “Upgrade this project to the latest Acme SDK and apply every migration step.”
• “What is Acme building next? Check their roadmap.”
• “Convert the changelog at github.com/vitejs/vite and tell me what breaks between Vite 6 and 8.”
• “We just shipped cursor pagination — publish it to our LogPulse changelog as 2.1.0 and mark the roadmap item shipped.”