MCP server

LivePublicator MCP server

Write a press release or announcement with Claude, ChatGPT or another AI assistant. LivePublicator checks it, shows you a preview, and after you confirm, publishes it in its newsroom with a live link in seconds.

How it works

Write. Your assistant writes the release with you: headline, one-sentence summary, body, key facts, a quote with the person's name and role, the press contact and an image if you have one.
Preview. LivePublicator checks it and gives you a private preview link, or a list of what to fix. You can see a preview without signing in.
Confirm. Nothing is published until you say so in the chat.
Live. You get the live link within seconds, and an email. Some releases are checked by a person first (up to 24 hours), see below.

Signing in and publishing need a LivePublicator account with credits. You manage credits and connected assistants in your account, never in the chat.

Connect it

Server address:

https://livepublicator.com/api/mcp

Claude (claude.ai and the desktop app): Settings, Connectors, Add custom connector. Paste the address, then click Connect and sign in.
ChatGPT: Settings, Apps and Connectors, Advanced, turn on Developer mode, then Create. Paste the address, choose OAuth, and sign in.
Other assistants and tools that support MCP: add a remote MCP server with this address. It uses OAuth 2.1 with PKCE and dynamic client registration.

When you sign in, you see what the assistant may do and choose Allow. You can disconnect it any time in your account.

What to ask

"Write a press release about our new product and publish it on LivePublicator."
"Announce our new office in Austin. Show me the preview first."
"Is my release live yet?"
"Fix the date in the release we published this morning."

Tools

Preview a press release preview_press_releaseShows how a company's press release or news announcement will look on LivePublicator, without signing in. Send the finished release: headline, one-sentence summary, body, key facts, a quote with the person's 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. No sign-in needed.

See your LivePublicator account get_accountShows the signed-in LivePublicator account: company or agency, the credits left for publishing press releases, whether releases go live after the automatic checks or wait for a person first, and for agencies the client companies.

Draft a press release create_releaseSaves a press release, launch announcement or other company news as a draft in the signed-in account and checks it: length, structure, links, image size and content. Send the finished release. LivePublicator does not write or change the text. Returns every problem to fix at once, or a private preview link. It does not publish and uses no credit. Company accounts can leave out the company name and website. Agencies name the client company and set client_authorized to true.

Change a draft press release update_releaseChanges 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.

Add a cover image add_imageAdds 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. The image must be landscape and at least 1200 px wide. Without an image, the release uses a simple cover with the company logo and headline, so this step is optional.

Publish a press release publish_releasePublishes a draft press release on LivePublicator 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.

Check a press release get_release_statusShows where a press release is: draft, waiting for a person to check it, scheduled or live, with the live link once it is published. Useful to check back on a release that was waiting for review.

List press releases list_releasesLists the account's latest press releases and announcements with their status and links.

Fix a live press release fix_live_releaseFixes 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.

Read: see your account, your credit balance and your releases.
Publish: create and preview releases, publish them (1 credit each, only after you confirm in the chat) and fix a live release's text within 24 hours.
We never ask for a password or an API key in the chat. You sign in with a one-time link we email you.

OAuth flow (technical)

Protected resource metadata: https://livepublicator.com/.well-known/oauth-protected-resource/api/mcp. A signed-in tool called without a token answers HTTP 401 with WWW-Authenticate: Bearer resource_metadata="…" (ChatGPT gets the same in the tool result's _meta).
Authorization server metadata: https://livepublicator.com/.well-known/oauth-authorization-server. Issuer https://livepublicator.com.
Clients: dynamic client registration at /api/oauth/register (RFC 7591), or a client ID metadata document (an https client_id URL).
Authorization code with PKCE (S256 only) at /oauth/authorize. Codes work once, for 5 minutes.
Tokens at /api/oauth/token: access tokens last 1 hour, refresh tokens 90 days and change on every use. Revocation at /api/oauth/revoke (RFC 7009), or Disconnect in the account.
Scopes: read and publish. Every tool lists its scheme in securitySchemes and carries readOnlyHint or destructiveHint.
Links the tools return all point to https://livepublicator.com.

When a person checks a release first

Company accounts signed in with an email on the company's own website: releases go live after our automatic checks.
Company accounts signed in with Gmail or another address: confirm a work email once in your account, or a person checks every release first (up to 24 hours).
Releases for another domain ending of your company's name are always checked by a person.
Agencies: the first 3 releases of a new connection, then some at random. Agencies confirm with each release that the client agreed.
Any release our automatic content check asks a person to look at.

If we don't publish a release, its credit comes back.

Images

Send an image link, attach a file in the chat where your assistant supports it, or use the one-time upload link the assistant gives you. Images must be landscape and at least 1200 px wide. No image is fine: the release gets a simple cover with your logo and headline. We never make AI images for these releases.

Privacy and support

We receive only what the assistant sends to our tools, not your other chats. See the privacy policy and the API terms. Support: support@livepublicator.com.