Connect Patchlog to Claude: A Step by Step Guide for Non-Developers

You do not need to be a developer to keep your changelog fresh. If you use the Claude desktop app, you can connect it to Patchlog once and then update your changelog by asking in plain English: "add a changelog entry about the new export feature and publish it." Claude does the clicking for you.

This guide assumes zero technical background. Every step is spelled out, and the whole thing takes about five minutes.

What you need before starting

1. A Patchlog account on the Pro plan. The connection uses Patchlog's API, which is a Pro feature.
2. The Claude desktop app installed on your computer (Windows or Mac), signed in to any paid Claude plan.

That is it. You do not need to install anything else: the Claude app fetches the Patchlog connector by itself.

Step 1: Get your Patchlog API token

A token is like a password that lets Claude act on your Patchlog account.

1. Log in to Patchlog in your browser.
2. Click your avatar in the bottom left, then go to Settings.
3. Open the API Tokens tab, or go straight to patchlog.io/settings/api-tokens.
4. Type a name for the token. "Claude" is a fine name.
5. Click create, then copy the token that appears. Paste it somewhere safe for a minute, like a note. You will not be able to see it again after you leave the page. If you lose it, no problem: revoke it and create a new one.

Step 2: Open Claude's connector settings

1. Open the Claude desktop app.
2. Open Settings. On Windows the gear icon lives in the bottom left; on Mac you can also press Cmd+Comma.
3. Look for the section called Connectors (in some versions it is under Developer, labeled "Edit Config").

If you found a "Connectors" section with an "Add custom connector" button, Claude may ask for a remote server URL. In that case you can use the hosted option, which is even easier: enter https://patchlog.io/mcp as the URL, and when asked for authentication choose a bearer token and paste your Patchlog token. Done, skip to Step 4.

If your version instead offers "Edit Config", continue to Step 3.

Step 3: Paste the configuration

The "Edit Config" button opens a file called claude_desktop_config.json in a text editor. It might be empty or already have some text.

If the file is empty, paste exactly this, then replace your-token-here with the token you copied in Step 1 (keep the quotes around it):

{
    "mcpServers": {
        "patchlog": {
            "command": "npx",
            "args": ["-y", "patchlog-mcp"],
            "env": {
                "PATCHLOG_API_TOKEN": "your-token-here"
            }
        }
    }
}

If the file already has a "mcpServers" section, add just the "patchlog" block inside it, next to the connectors that are already there.

One extra requirement for this route: the npx command comes with Node.js, so if Claude reports it cannot find npx, install Node.js from that page (the LTS button, all defaults) and restart your computer. The hosted URL option in Step 2 avoids this entirely.

Save the file, then fully quit Claude and open it again. On Windows, right click the Claude icon in the system tray and choose Quit; just closing the window is not enough.

Step 4: Check it works

Start a new chat in Claude and type:

List my Patchlog projects

The first time, Claude will ask for permission to use the Patchlog connector. Allow it. If everything is wired up, Claude replies with your project names and their changelog links.

What you can now say to Claude

• "Add a changelog entry to [project] about the new pricing page. Keep it as a draft."
• "Show me my draft entries and read me the latest one."
• "Fix the typo in that draft, change 'recieve' to 'receive', then publish it."
• "Schedule an entry about the maintenance window for Friday 8am."

Two safety notes worth knowing. Entries Claude creates are drafts unless you explicitly say publish, so nothing goes public by accident. And the token only reaches your own projects, and you can revoke it any time from the same settings page, which instantly cuts Claude's access.

If something does not work

• Claude says it has no Patchlog tools. The app was not fully restarted, or the config file has a typo. Quit completely and reopen; if that fails, re-paste the config from Step 3.
• Claude says the token is invalid. The token was pasted with a missing character, or it was revoked. Create a fresh one and update the config.
• Claude says the API is a Pro feature. Your Patchlog account is on the Free plan. Upgrade on the pricing page.

If you are a developer or you live in the terminal, the main MCP guide covers Claude Code and Cursor in two commands.