<?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: Mike Lawrence</title>
    <description>The latest articles on DEV Community by Mike Lawrence (@maevesocial).</description>
    <link>https://dev.to/maevesocial</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%2F4089232%2F39e2166d-e8bf-4d95-b794-903c17729a26.png</url>
      <title>DEV Community: Mike Lawrence</title>
      <link>https://dev.to/maevesocial</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/maevesocial"/>
    <language>en</language>
    <item>
      <title>Managing social media workflows with MCP, API, and CLI</title>
      <dc:creator>Mike Lawrence</dc:creator>
      <pubDate>Sat, 22 Aug 2026 06:14:43 +0000</pubDate>
      <link>https://dev.to/maevesocial/managing-social-media-workflows-with-mcp-api-and-cli-1213</link>
      <guid>https://dev.to/maevesocial/managing-social-media-workflows-with-mcp-api-and-cli-1213</guid>
      <description>&lt;p&gt;Social media work rarely fits neatly into a developer workflow. A post starts in a brief, moves through writing and review, needs assets, gets scheduled, and later turns into reporting. Teams often split that work across several apps and a spreadsheet.&lt;/p&gt;

&lt;p&gt;I’m working on &lt;a href="https://maevesocial.com" rel="noopener noreferrer"&gt;Maeve Social&lt;/a&gt;, a social media management platform that puts those stages in one system and also supports API, CLI, and MCP automation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where MCP fits
&lt;/h2&gt;

&lt;p&gt;Maeve Social exposes an MCP endpoint at:&lt;br&gt;
&lt;/p&gt;

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

&lt;/div&gt;



&lt;p&gt;That gives compatible agent workflows a direct integration point alongside the platform’s API and CLI. The aim is to let automated workflows participate in the same content process that people use, instead of maintaining a separate automation-only pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  The workflow around the automation
&lt;/h2&gt;

&lt;p&gt;The product includes a content calendar and board, a Workbench for briefs and scripts, a media library, internal approvals, and client review links. Clients can review content without creating an account.&lt;/p&gt;

&lt;p&gt;Approved content can be published to Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Threads, Pinterest, and Google Business Profile. Maeve also includes a unified social inbox, Instagram grid planning, analytics, branded PDF reports, and an AI assistant.&lt;/p&gt;

&lt;p&gt;The useful part for developer-led teams is that the API, CLI, and MCP options sit beside those human review steps. Automation can support the workflow without removing the point where a person checks the content.&lt;/p&gt;

&lt;h2&gt;
  
  
  Current availability
&lt;/h2&gt;

&lt;p&gt;Maeve Social is web-based. Paid plans are Basic at $25 per month, Standard at $99 per month, and Premium at $199 per month. There is a three-day trial, but no permanent free plan.&lt;/p&gt;

&lt;p&gt;You can see the product at &lt;a href="https://maevesocial.com" rel="noopener noreferrer"&gt;maevesocial.com&lt;/a&gt; and the current pricing at &lt;a href="https://maevesocial.com/pricing" rel="noopener noreferrer"&gt;maevesocial.com/pricing&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>api</category>
      <category>automation</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
