ReleasePad - Release notes, written for you

Your team ships code every week.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Create Category: Creates a category in a product. Categories group posts and show as a colored badge next to each post on the changelog; background_color is the badge color. Check list_categories firs
  • Create Post: Creates a release note in a product. The body is GitHub-flavoured Markdown, stored verbatim, and must be at least 100 characters. Call list_categories first: every post needs a category_i
  • Delete Category: Deletes a category. Its posts are kept and still point at it; the category just stops being listed and offered for new posts. It cannot be restored through this server, so confirm wit

What data it sees

Do you need an account

No: the server works without sign-in

Your team ships code every week. Your users find out... eventually.

Release notes are the first thing to slip when a launch is busy. The feature is out, the changelog is quiet, and the people who asked for it never hear that it arrived.

With ReleasePad in ChatGPT/Codex, writing them stops being a chore. Paste the pull request, the ticket, or a few bullet points and say "write the release note." Your agent drafts it in your product's voice, files it under the right category, and saves it to your ReleasePad changelog.

You read it, tweak a line if you like, and say "publish." It is live on your changelog page and in your in-app widget.

That is the everyday win. There is more once you get going:

  • Never lose track of what shipped. Ask "what did we release in August?" or "is the SSO post still a draft?" and get the answer from your own changelog.
  • Plan the launch, not just the post. Write it today, schedule it for release day, and move on.
  • Polish old posts in seconds. "Make this friendlier," "add a screenshot link," "split this into two posts."
  • See who is reading. Find out which posts get attention and where your readers are.

You stay in charge. Every post your agent writes starts as a draft, so nothing reaches your users until you approve it. Prefer that your agent only reads? Grant read-only access and it becomes a research assistant for your changelog.

Connect in one click with your ReleasePad login. No keys to copy, and you can disconnect any time from your account settings.

ReleasePad is the changelog tool for product teams who want users to notice what they build. This plugin is available on paid ReleasePad plans.

Server tool list (15)

Raw names from tools/list. Only developers need these.

create_categoryCreates a category in a product. Categories group posts and show as a colored badge next to each post on the changelog; background_color is the badge color. Check list_categories first to avoid creating a duplicate. Returns the created category, including the id that create_post takes as category_id.
create_postCreates a release note in a product. The body is GitHub-flavoured Markdown, stored verbatim, and must be at least 100 characters. Call list_categories first: every post needs a category_id from the same product. The post is saved as a draft unless draft=false is passed; a published post appears on the public changelog as soon as publish_at (default: now) has passed. Returns the created post, including the id that update_post and delete_post take.
delete_categoryDeletes a category. Its posts are kept and still point at it; the category just stops being listed and offered for new posts. It cannot be restored through this server, so confirm with the user before calling. Returns the id with deleted=true.
delete_postDeletes a post. It disappears from the public changelog and from these tools and cannot be restored through this server, so confirm with the user before calling. To hide a post temporarily, use update_post with draft=true instead. Returns the id with deleted=true.
get_categoryReturns one category by its numeric id: name, badge color and product. Use list_categories when the id is not known yet.
get_postReturns one post by its numeric id, including its full Markdown body, blurb, category, draft flag, publication date and view count. Use it to read a post before editing it with update_post, or when list_posts would return more than needed.
get_productReturns one product from the caller's account by its numeric id, with the same fields as list_products. Use list_products when the id is not known yet.
list_categoriesLists a product's categories, sorted by name, without pagination. Categories group posts (for example New, Improvement, Fix) and show as a colored badge on the changelog. The `id` of each category is the category_id that create_post and update_post take.
list_changelog_viewsLists the individual views of a product's public changelog page (ip, country, city, timestamp), newest first, 10 per page, for audience analytics. country and city are filled in asynchronously and are null for recent views. The pagination count is the total number of page views.
list_post_viewsLists the individual views of one post (ip, country, city, timestamp), newest first, 10 per page, for audience analytics. country and city are filled in asynchronously and are null for recent views. For the total only, use view_counter from get_post instead of paging through this.
list_postsLists a product's posts (release notes), newest first, 45 per page, with optional filters by status, title and category. Every post comes with its full Markdown body, so use the filters to find specific posts instead of paging through everything. Status meanings: published is visible on the public changelog, draft is not visible, to_be_published has a publish_at in the future, all is everything.
list_productsLists the products in the caller's ReleasePad account, newest first, 10 per page. Call this first: the `id` of each product is the `product_id` every other tool needs. Each product includes its name, website, public changelog slug (product_uri), posts_count and logo.
update_categoryRenames a category or changes its badge color. Partial input: fields left out keep their current value. The change shows on every post in the category. Returns the updated category.
update_postUpdates a post. Partial input: only the fields sent change, the rest keep their current values, so send just what should change. A new body replaces the whole body, so read the post with get_post first when editing part of it. Set draft=false to publish a draft (visible immediately, or at publish_at if that is in the future) and draft=true to take a post off the changelog. Returns the updated post.
upload_imageStores an image for use in a post body and returns its public URL. Send the image bytes as base64 (plain or as a data: URL); PNG, JPEG, GIF, WebP and SVG are accepted, 5 MB maximum, and the type is detected from the bytes. Reference the returned url in Markdown as ![alt text](url) when calling create_post or update_post. Every call stores a new file under a fresh name, so upload an image once and reuse the url.