<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: LivePublicator</title>
    <description>The latest articles on DEV Community by LivePublicator (@livepublicator).</description>
    <link>https://dev.to/livepublicator</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4200394%2Fe8609eae-28d4-4d02-958c-474d45591edb.png</url>
      <title>DEV Community: LivePublicator</title>
      <link>https://dev.to/livepublicator</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/livepublicator"/>
    <language>en</language>
    <item>
      <title>How to publish a press release from Claude, ChatGPT or Cursor (MCP)</title>
      <dc:creator>LivePublicator</dc:creator>
      <pubDate>Thu, 22 Oct 2026 11:49:31 +0000</pubDate>
      <link>https://dev.to/livepublicator/how-to-publish-a-press-release-from-claude-chatgpt-or-cursor-mcp-526m</link>
      <guid>https://dev.to/livepublicator/how-to-publish-a-press-release-from-claude-chatgpt-or-cursor-mcp-526m</guid>
      <description>&lt;p&gt;Most product news dies in a Slack thread. The feature ships, someone says "we should announce this", and a week later nobody has written anything.&lt;/p&gt;

&lt;p&gt;If you already work in an AI assistant all day, you can write and publish the announcement there, in the same chat where you described the feature. This guide shows how with LivePublicator's remote MCP server.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you get
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A full press release drafted from what is already in your chat: headline, one-line summary, body, key facts and a short FAQ.&lt;/li&gt;
&lt;li&gt;A private preview link to check it before anything goes public.&lt;/li&gt;
&lt;li&gt;One explicit publish step, and the live link back in the chat.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Previews are free and need no account. Publishing uses a credit from your LivePublicator account.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Connect the server
&lt;/h2&gt;

&lt;p&gt;The server URL is the same everywhere:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://livepublicator.com/api/mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Claude (claude.ai or Desktop):&lt;/strong&gt; Settings, Connectors, Add custom connector, paste the URL.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Claude Code:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude mcp add &lt;span class="nt"&gt;--transport&lt;/span&gt; http livepublicator https://livepublicator.com/api/mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Cursor and other clients&lt;/strong&gt; (&lt;code&gt;mcp.json&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"mcpServers"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"livepublicator"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"https://livepublicator.com/api/mcp"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;ChatGPT:&lt;/strong&gt; turn on developer mode (Settings, Apps), create an app with the URL, and sign in.&lt;/p&gt;

&lt;p&gt;Sign-in is OAuth 2.1 with PKCE. Your client opens the sign-in page the first time you use a tool that needs it.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Ask for the release
&lt;/h2&gt;

&lt;p&gt;You can start from one line, or from something already in the chat:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Publish a press release about the CSV export we shipped today.&lt;/p&gt;

&lt;p&gt;Turn this blog post into a press release.&lt;/p&gt;

&lt;p&gt;We just hired a new CTO. Announce it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The assistant drafts the whole release itself from the chat and your own pages. It should only ask you for what it cannot know: the news itself if you only gave a topic, who the quote is from, and the press contact if none is saved.&lt;/p&gt;

&lt;p&gt;Two rules worth knowing: the server never invents numbers, names or dates, and the person quoted has to approve their quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Check the preview
&lt;/h2&gt;

&lt;p&gt;Before anything is public you get a preview link and a list of the key facts and FAQ the assistant wrote. Change anything in the chat, or open the draft page and edit it there. Every release goes through the same checks as the website, and some are held for a person to review before they go live.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Publish
&lt;/h2&gt;

&lt;p&gt;Publishing is a separate tool that only runs after you clearly say so. The assistant then returns the live link, or tells you if the release is waiting for a review and roughly how long that takes. Within 24 hours of going live you can still fix the text from the chat.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tools
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Sign-in&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;preview_press_release&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Checks a finished release and returns every problem at once, or a private preview link. Publishes nothing.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;get_account&lt;/code&gt;, &lt;code&gt;get_release_status&lt;/code&gt;, &lt;code&gt;list_releases&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Read&lt;/td&gt;
&lt;td&gt;Credits, status and your releases.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;create_release&lt;/code&gt;, &lt;code&gt;update_release&lt;/code&gt;, &lt;code&gt;add_image&lt;/code&gt;, &lt;code&gt;publish_release&lt;/code&gt;, &lt;code&gt;fix_live_release&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Publish&lt;/td&gt;
&lt;td&gt;Save, change and publish a release, add a cover, fix a live one.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Why a press release at all?
&lt;/h2&gt;

&lt;p&gt;Your website says what you do. A dated, specific page says what is new: what happened, where, when, who said what. That is the kind of page people, search engines and AI assistants can point to when someone asks about your company. Nobody can promise what an assistant will say, but you can control the quality of the sources it finds.&lt;/p&gt;

&lt;p&gt;Docs: &lt;a href="https://livepublicator.com/docs/mcp" rel="noopener noreferrer"&gt;https://livepublicator.com/docs/mcp&lt;/a&gt;&lt;br&gt;
Setup guide: &lt;a href="https://livepublicator.com/publish-from-ai" rel="noopener noreferrer"&gt;https://livepublicator.com/publish-from-ai&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>productivity</category>
      <category>marketing</category>
    </item>
  </channel>
</rss>
