Official MCP RegistryListed
LivePublicator
Write, preview and publish your company's press releases from the chat, with a live link in seconds.
First seen 16 Oct 2026. Evidence as of 18 Oct 2026.
9
Tools
From an anonymous probe
1
Source listings
Each with its own history
31
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| add_image | Adds a cover image to a draft press release. Send an image URL, or a file the user attached in the chat. With neither, it returns a one-time upload link where the user can drop the image. An image 1200 px wide or more fills the page, and from 600 px it shows at its own size. Under 600 px, or without an image, the release uses a simple cover with the company logo and headline, so this step is optional. | Changes data |
| create_release | Saves a company's press release as a draft in the signed-in account and checks it: length, structure, links, image size and content. Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat. The company, press contact and spokesperson come from the account when you leave them out. Send the image too: image_url, or image_file for a file attached in the chat, with image_is_ai true when it was made with AI. LivePublicator does not change the text. Returns every problem to fix at once, or a private preview link and an edit link. It does not publish and uses no credit. Agencies name the client company and set client_authorized to true. | Changes data |
| fix_live_release | Fixes the text of a published press release within 24 hours of it going live: a typo, a wrong date, a link, the quote. Send only the fields to change. The release keeps the same link and the earlier version is kept. The change is checked again before it shows. After 24 hours the text can't be changed. | Destructive |
| get_account | Shows the signed-in LivePublicator account: the company, the saved press contact and spokesperson (create_release fills these in, so do not ask the user for them), what is still missing, the credits left, whether releases go live after the automatic checks or wait for a person, and for agencies the client companies. Call it once before drafting. | Read-only |
| get_release_status | Shows where a press release is: draft, waiting for a person to check it, scheduled or live, with the live link once it is published. Only when the user asks about a release later. Not needed after create_release or publish_release, whose answers already say this. | Read-only |
| list_releases | Lists the account's earlier press releases with their status and links. Only when the user asks about their earlier releases. Not needed to draft or publish a new one. | Read-only |
| preview_press_release | Shows how a company's press release will look on LivePublicator, without signing in. Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat: headline, one-sentence summary, body, key facts and questions and answers, plus the quote (name and role), press contact, company name and website, and an image URL if there is one. Returns every problem to fix at once, or a private preview page that expires after 7 days. The preview page has a button to publish it on the LivePublicator website. This tool publishes nothing. | Read-only |
| publish_release | Publishes the latest saved version of a draft press release on LivePublicator, including changes the user made on the draft page, and tells search engines about it. Only call this after the user has seen the preview and clearly said to publish, and set confirm to true. Uses 1 credit. Returns the live link within seconds, or says the release is waiting for a person to check it, with the reason and the expected time (up to 24 hours). If LivePublicator does not publish it, the credit comes back. | Destructive |
| update_release | Changes fields of a draft press release (only the fields you send) and checks the whole release again. Returns the problems to fix, or the updated preview link. Uses no credit. | Changes data |
Change history
- list_releases: description changed (+"earlier" +"Only when the user asks about their earlier releases. Not needed to draft or publish a new one." -"latest")
- get_release_status: description changed (+"Only when the user asks about" +"later. Not needed after create_release or publish_release, whose answers already say this." -"Useful to check back on")
- server instructions changed (+"before drafting," +"Do not call list_releases or open preview links unless the user asks about past releases. A normal release takes three calls: get_account, create_release, publish_release." +"With no credits left, drafts and previews still work. Only publish_release needs a credit. If it says none")
- Repository changed (registry)
- update_release: title changed
- update_release: annotations changed
- publish_release: title changed
- publish_release: description changed (+"the latest saved version of" +"LivePublicator, including changes the user made on the draft page," -"LivePublicator")
- publish_release: annotations changed
- preview_press_release: title changed
- preview_press_release: input schema changed (+image_is_ai)
- preview_press_release: description changed (+"Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from" +"chat:" +"facts and questions and answers, plus the")
- preview_press_release: annotations changed
- list_releases: title changed
- list_releases: annotations changed
- get_release_status: title changed
- get_release_status: annotations changed
- get_account: title changed
- get_account: description changed (+"the company, the saved press contact and spokesperson (create_release fills these in, so do not ask the user for them), what is still missing," +"left," +"person,")
- get_account: annotations changed
- fix_live_release: title changed
- fix_live_release: input schema changed (+image_is_ai)
- fix_live_release: annotations changed
- create_release: title changed
- create_release: input schema changed (+image_file, +image_is_ai)
- create_release: description changed (+"company's" +"release" +"Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat. The company, press contact and spokesperson come from the account when you leave them out.")
- create_release: annotations changed
- add_image: input schema changed (+image_is_ai)
- add_image: description changed (+"An" +"1200 px wide or more fills the page," +"from 600 px it shows")
- server instructions changed (+"The user may start with one line ("a" +"about our new feature") or" +"something already in this chat, such as a blog post, notes or a page. Draft")
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.livepublicator/livepublicator | 16 Oct 2026 | 18 Oct 2026 | 2 |