MCP server for AI agents

Built for organic growth. Your post on your blog, Dev.to, LinkedIn profile, Bluesky, Mastodon and X, on autopilot.

One post becomes your blog plus Dev.to, your LinkedIn profile, Bluesky and more, all pointing back to your site, so search and AI assistants can find you.

X needs your own API keys.

Illustrative example · Pro plan shown

In your chat

Illustrative example: in your chat, you ask your AI assistant to write 5 posts on a topic your customers ask about for your blog and schedule them for next week. It replies that 5 posts are drafted and scheduled, your blog first, then 6 platforms, and five posts appear, one for each day from Monday to Friday.

Your week, on autopilot

Illustrative example: across next week, Monday to Friday, each post is published on yoursite.com first, marked as the original, then on Dev.to, Hashnode, your LinkedIn profile, Bluesky, Mastodon and X, each copy linking back to yoursite.com.

Where your customers can find you

Illustrative example

Illustrative example, not a real search result: a customer asks which software to choose. An AI answer summarises a comparison on yoursite.com, lists a page on yoursite.com as a source, and shows your product with a link to yoursite.com. Results depend on your content and the search engine.

Built on MCP, the open standard many AI assistants support.

Tested with Claude Code. Any assistant that supports remote MCP servers can connect.

Assistants whose docs list remote MCP support

  • Claude
  • Claude Code
  • OpenAI Codex
  • Cursor
  • VS Code
  • Gemini CLI
  • Windsurf
  • Zed
  • JetBrains AI Assistant
  • Cline
  • Roo Code
  • Goose
  • Warp
  • Kiro
  • Amp
  • Continue

and more

How to connect your assistant

What it looks like once scatterpost is running

Every example below is illustrative, with yoursite.com standing in for your site and you as the author.

01

Found in search

Someone searches for the thing you know. Your post on your own site can be the one they land on, with the copies on Dev.to and Hashnode pointing back to it rather than competing with it.

Your own site is the original. Copies point back to it. Where it ranks is up to the search engine.

Illustrative example: a customer searches for which software to choose. Your post on yoursite.com appears as the original, alongside the copies on Dev.to and Hashnode, each marked as linking to yoursite.com. Where any page ranks is up to the search engine.

02

Ready for AI assistants

When someone asks an assistant instead of searching, clear, well-structured posts on your own site are easier for an assistant to read, and a post it can read is one it can point to.

llms.txt and structured data can help assistants read and quote your posts.

Illustrative example: a customer asks an AI assistant which software to choose. In this example, the answer draws on your post and shows a source link to a page on yoursite.com.

03

Your week, published

Monday, your assistant drafts. Tuesday, the post goes live on your site as the original. Through the rest of the week, a copy goes out to each platform you connect, on your schedule.

Every copy links back to yoursite.com.

Illustrative example of a week. Monday: your assistant writes a draft. Tuesday: it is published on yoursite.com as the original. Wednesday to Friday: copies go out to Dev.to, Hashnode, your LinkedIn profile, Bluesky, Mastodon and X, each linking back to yoursite.com. The Dev.to copy shows Originally published at yoursite.com.

04

Watch it add up

Each post adds another page on your site and another copy pointing home. The dashboard shows posts, platforms and clicks back to your site in one place, so you can see what worked.

One place to see what each post did, across every platform.

Illustrative example of a month, not real results: 20 posts published, 7 platforms including your own site, and 400 clicks back to your site, with a small chart of clicks by day.

Illustrative figures, not typical or real results. Yours depend on your content.

What you can ask it

One sentence in your chat, and scatterpost does the rest.

You: Write a blog post about our new features and publish it everywhere.

Assistant: Drafted: “Three features worth telling founders about”

  • Published on yoursite.com first
  • Dev.to, links back to your site
  • Hashnode, links back to your site
  • LinkedIn profile, links back to your site
  • Bluesky, links back to your site

Works in Claude, Claude Code, Cursor or any MCP client

No blog yet? Start from a template

Four ready-made blogs, pre-configured for AI and search, so you skip the setup and start publishing. Pick one, deploy it to your own Vercel account, and customise anything.

  • Ready for your AI agent

    scatterpost can publish to it from Claude, Cursor or any MCP client as soon as you paste in one secret. No webhook code to write.

  • Easy for AI assistants to read

    Every post ships with structured data and an llms.txt file, so AI assistants can understand and quote your writing.

  • Set up for search

    Sitemap, RSS feed, canonical links and social preview images come built in. Add a key and new posts ping IndexNow too.

  • Yours to own and change

    Your domain, your Vercel account, MIT licence. Light and dark mode and a cookie consent banner are already done.

Minimal template preview

Minimal

A calm, editorial blog for founders who write.

Developer template preview

Developer

An engineering notebook: code blocks, callouts and tag pages.

Magazine template preview

Magazine

An image-led publication for longer pieces.

Changelog template preview

Changelog

A product changelog with versions and New, Improved, Fixed tags.

See all templates

MCP server

Quick connect

Two steps, and your AI assistant can publish for you.

1.Create an API key

Create an API key

Free account, no card needed.

2.Copy this into your AI assistant

Install the scatterpost MCP server for me. My API key is PASTE_YOUR_KEY_HERE. Follow the setup steps at https://app.scatterpost.io/docs/mcp for my assistant, then confirm the scatterpost tools are available.

Manual setup
  1. Create an API key in scatterpost: Settings, API keys and apps.

  2. Paste this into Claude Code, with your key in place of PASTE_YOUR_KEY_HERE:

    Prompt

    Install the scatterpost MCP server for me. Run: claude mcp add scatterpost -e SCATTERPOST_API_KEY=PASTE_YOUR_KEY_HERE -- npx -y @scatterpost/mcp and replace PASTE_YOUR_KEY_HERE with my key, then confirm the scatterpost tools are available.

    Or run it yourself in a terminal:

    Command
    claude mcp add scatterpost -e SCATTERPOST_API_KEY=PASTE_YOUR_KEY_HERE -- npx -y @scatterpost/mcp

Works with Claude, Claude Code, Cursor or any assistant that supports MCP.

Syndication destinations

Where it publishes

Unlimited channels on Pro and Team; plans are gated on scheduled posts, not on how many you connect.

Your websiteOriginal

Publishes first, over a webhook your site exposes. The URL it reads back is what every cross-post points to.

Format: MarkdownPublishes first
Dev.toDev.tolive

Posted through the Dev.to API with canonical_url set to your website's URL.

Format: Forem MarkdownLinks back
Hashnodelive

Posted through the Hashnode API with the republished-from field set to your website's URL.

Format: MarkdownLinks back
LinkedInLinkedIn profilelive

Posted as a text update with a link back to your site when your site is connected.

Format: Text updateLinks back
Blueskylive

Posted via the AT Protocol as a single post with the composed text and a link back, truncated at a word boundary to fit.

Format: Single postLinks back
MastodonMastodonlive

Posted to your instance via the Mastodon API as a single post with the composed text and a link back, truncated at a word boundary to fit.

Format: Single postLinks back
X (formerly Twitter)live

Posted using your own X API keys, split into a thread when the article runs long. X charges for API access on its own side; scatterpost does not add a markup.

Format: ThreadYour own API keys
Comingin progress

Not available yet, planned for a future release.

Threads (coming)Medium (coming)LinkedIn Page (awaiting LinkedIn approval)

LinkedIn Page: Posting to company Pages needs LinkedIn to approve scatterpost. Until then, post from your profile and reshare to your Page.

Assisted, you post it (coming)

scatterpost prepares the post and checks the community's rules; you post it yourself.

Hacker NewsProduct HuntIndie HackersReddit

Pricing

Unlimited channels on Pro and Team

No VAT is added.

Free
£0
  • ✓1 workspace
  • ✓3 connected channels
  • ✓5 scheduled posts a month
Start free
Pro
£19 a month per workspace
  • ✓Unlimited channels and posts
  • ✓Scheduling with local-time slots
  • ✓Analytics
Choose Pro
Team
£49 a month per workspace
  • ✓Everything in Pro
  • ✓3 seats included, then £10 a seat
  • ✓Approval workflow
Choose Team

Full pricing and FAQ

Stop pasting articles across tabs.

Connect scatterpost to your agent, publish to your own site first, and cross-post everywhere else with a link back to the original.

Get started