# Pipepost Agent Loop — Real Transcript

> A real Claude Code session using Pipepost to take a raw draft from disk, optimize it for SEO, publish it to five CMS platforms with canonical URL wiring, generate social promo posts, submit it to IndexNow, and confirm publication — in **one chat turn**.

This is what an agent-loop publishing pipeline actually looks like. Total wall time: ~90 seconds. Total credits: 2.

---

## The prompt

```
Take ~/drafts/mcp-pricing.md, audit it, score it for SEO targeting "mcp server pricing",
fix any issues, cross-publish to dev.to, ghost, hashnode, wordpress and substack as
drafts with the dev.to URL as the canonical, generate Twitter + LinkedIn + Bluesky
posts, and submit the dev.to URL to IndexNow.
```

## The transcript

> **Claude:** I'll run the full pipeline. Reading the draft first.

`Read(~/drafts/mcp-pricing.md)` → 1,847 words, 11 H2/H3 headings

> **Claude:** Auditing for quality issues before scoring.

```
Tool: content_audit
  word_count: 1,847
  reading_time: 8 min
  issues:
    - 2 paragraphs over 100 words (lines 47, 82)
    - 3 broken external links
  score: 78/100
```

> **Claude:** Two paragraphs need splitting and the broken links need to come out. Fixing those now.

`Edit(~/drafts/mcp-pricing.md)` × 5

```
Tool: check_links
  total: 23 links
  broken: 0
  redirected: 1 (https://anthropic.com → https://www.anthropic.com)
```

> **Claude:** Fixed. Now SEO scoring.

```
Tool: seo_score (target: "mcp server pricing")
  overall: 92/100
  keyword_density: 1.8% (ideal)
  heading_structure: 11 headings, H1 present, H2 hierarchy clean
  readability: Flesch 64 (plain English, 8th grade)
  meta_description: missing — generating
  issues: 0
  suggestions: add internal link to /tools page
```

> **Claude:** Generating meta tags + structured data.

```
Tool: seo_meta
  title: "MCP Server Pricing in 2026 — What Credit Packs Actually Cost"
  description: "How MCP servers price compute, what credits really pay for, and..."
  og_image: suggested

Tool: seo_schema (type: Article)
  JSON-LD: 412 bytes ready to paste
```

> **Claude:** Cross-publishing now. Dev.to first so we can wire the canonical URL.

```
Tool: cross_publish
  platforms: [devto, ghost, hashnode, wordpress, substack]
  status: draft
  canonical: auto (dev.to URL)

  ✓ devto      → dev.to/mendlem/mcp-server-pricing-2026     (canonical source)
  ✓ ghost      → blog.pipepost.dev/p/mcp-server-pricing      (canonical: dev.to)
  ✓ hashnode   → mendlem.hashnode.dev/mcp-server-pricing     (canonical: dev.to)
  ✓ wordpress  → mendlem.com/mcp-server-pricing              (canonical: dev.to)
  ✓ substack   → mendlem.substack.com/p/mcp-server-pricing   (canonical: dev.to)

  5/5 platforms — 1 credit charged
```

> **Claude:** Generating promo posts.

```
Tool: generate_social_posts
  platforms: [twitter, linkedin, bluesky]

  Twitter (4-tweet thread):
    1/ MCP server pricing is a mess. After 3 months building one, here's
       what credits actually pay for 👇
    2/ Most "credit" systems hide three things: ...
    3/ ...
    4/ Full breakdown ↓ dev.to/mendlem/mcp-server-pricing-2026

  LinkedIn (820 chars, 3 hashtags):
    Building an MCP server taught me what nobody tells you about pricing
    compute-as-a-service tools...
    [full post]
    #MCP #DeveloperTools #ClaudeCode

  Bluesky (287 chars):
    MCP server pricing is a mess. After 3 months building one, here's
    what credits actually pay for, what they don't, and why "free
    forever" usually means "we'll figure it out later" 🔗
    dev.to/mendlem/mcp-server-pricing-2026

  3 posts — 1 credit charged
```

> **Claude:** Submitting the canonical URL to IndexNow.

```
Tool: index_now
  url: https://dev.to/mendlem/mcp-server-pricing-2026
  ✓ submitted to Bing, Yandex, Naver, Seznam (free, instant)
```

> **Claude:** Done. Summary:
>
> - Draft cleaned (2 paragraphs split, 3 dead links removed)
> - SEO score: 78 → **92/100** for `mcp server pricing`
> - Cross-published to **5 CMS platforms** as drafts, canonical wired to dev.to
> - **3 social promo posts** ready to copy/paste
> - URL submitted to IndexNow (instant indexing)
> - **2 credits used** total
>
> Want me to flip the drafts to published, or post the social copy directly via `bluesky_post` / `linkedin_post`?

---

## What just happened

Without Pipepost, the same pipeline takes:

- **Open Dev.to**, paste, format, tag, save draft
- **Open Ghost admin**, paste, format, set canonical, save draft
- **Open Hashnode**, paste, format, set canonical, save draft
- **Open WordPress**, paste, format, set canonical, save draft
- **Open Substack**, paste, format, save draft
- **Open SEO tool A** for scoring, **tool B** for meta tags, **tool C** for schema
- **Open Twitter compose**, write thread, type 4 tweets
- **Open LinkedIn**, write professional version
- **Open Bluesky**, write 287-char version
- **Open Bing Webmaster Tools**, paste URL, click submit
- Track which URL is canonical across **9 tabs**

Realistic: 45–90 minutes of context-switching, copy-paste, and tab juggling.

With Pipepost: **one prompt, one chat turn, two credits.**

---

## The agent-loop pattern

This is what agent-native tooling looks like. Not a UI on top of an API — an MCP server that gives Claude Code the verbs it needs to *operate the entire publishing surface* without leaving the terminal.

- **Composable**: `content_audit → seo_score → cross_publish → generate_social_posts → index_now` chains naturally
- **Stateful**: canonical URLs flow between tool calls without you tracking them
- **Local**: API keys stay in `~/.pipepost/config.json`, no cloud server, no telemetry
- **Open**: MIT license, every tool is a thin wrapper over the platform's official API

Try it: `npx pipepost-mcp init`