shipped streamable http transport for blurt mcp. rackup, puma, the whole song and dance. your vps runs mcp on /mcp, claude code talks to it remotely. no more ssh tunnel sorcery. blurt.sh #ai #webdev #indiedev #buildinpublic
Posts by Florent #buildinpublic
blurt mcp has 7 tools now. claude code can list-queue, create-post, publish-now, delete-post, the works. plus 2 resources for live queue state. full crud from inside my editor. cursed magic. blurt.sh #ai #webdev #indiedev #buildinpublic
phase 2 of blurt was supposed to ship apr 6. it shipped apr 15. 9 days late. nobody's paying me and yet somehow there's still a deadline i blew through. finishing the rest this week. v0.2.0 drops soon. blurt.sh #ai #webdev #indiedev #buildinpublic
Took a break in the development of blurt.sh for enjoying my new coffee toys
#coffee #coffeesky #buildinpublic #indiedev
phase 2 done. CLI and MCP server ship.
two weeks ago this was a markdown parser. now it publishes to 6 platforms from your terminal, your editor, or a folder
next: web dashboard so you can see your queue without a terminal
blurt.sh
#OpenSource #IndieDev #BuildInPublic #SelfHosted
blurt now has three input methods:
drop a .md file in queue/
blurt post from your terminal
ask your AI editor via MCP
all hit the same engine. all publish to 6 platforms. all store permalinks in your files
blurt.sh
#OpenSource #IndieDev #BuildInPublic #SelfHosted
published a post to 3 platforms from Claude Code today.
no browser. no copy-paste. told the AI "post this to bluesky, mastodon, and linkedin" and blurt's MCP server handled it
this is what AI-native tooling looks like
blurt.sh
#OpenSource #IndieDev #BuildInPublic #SelfHosted
the blurt CLI is just an HTTP client. no rails dependency. no database access.
point it at localhost:3000 or your VPS. same commands, same output
your server is the source of truth. the CLI is a window into it
blurt.sh/docs/cli
#OpenSource #IndieDev #BuildInPublic #SelfHosted
Are morning routines still a thing?
built an MCP server for blurt.
your AI editor can now publish to 6 platforms. Claude Code, Cursor, Windsurf โ any MCP client.
"publish this to bluesky and mastodon" and it just does it
blurt.sh
#OpenSource #IndieDev #BuildInPublic #SelfHosted
I miss it because I used it 1 month before going back to Ecosia
The experience was so so great tho
Iโm not sure I understand what you mean
you can publish from your terminal now.
blurt post "hello world" --platforms bluesky,mastodon
one command. hits the API. post lands in queue, gets published, moves to sent/ with permalinks
blurt.sh/docs/cli
#OpenSource #IndieDev #BuildInPublic #SelfHosted
blurt has a CLI now.
blurt status โ server health, queue counts, platforms
blurt queue โ see what's pending
it talks to the HTTP API. works local, works remote. same engine, new interface
blurt.sh/docs/cli
#OpenSource #IndieDev #BuildInPublic #SelfHosted
$2 trillion wiped from SaaS valuations. the tools that survive own the system of record.
for social publishing, nobody owns that today. your buffer history lives in their database.
blurt keeps it as files on your machine
github.com/fberrez/blurt.sh
#OpenSource #IndieDev #FOSS #SelfHosted
$2 trillion wiped from SaaS valuations. the tools that survive own the system of record.
for social publishing, nobody owns that today. your buffer history lives in their database.
blurt keeps it as files on your machine
github.com/fberrez/blurt.sh
#OpenSource #IndieDev #FOSS #SelfHosted
Screenshot of the blurt.sh landing page โ bold headline reading "Markdown in, posts everywhere." with a waitlist email signup form, open-source and MIT licensed badges, on a clean minimal white background
day 5 of building blurt in public.
rails 8 backend with 6 platform publishers. filesystem queue. markdown in, posts everywhere.
the landing page is up, waitlist is collecting emails, and the core engine is taking shape.
join the waitlist: blurt.sh
#buildinpublic #webdev #indiedev
Install a custom ROM like @grapheneos.org or @murena-com.bsky.social
We use Umami for analytics. If you have something that I could plug to Umami, I might be interested
building blurt's HTTP API today. every input method โ CLI, MCP server, web dashboard โ talks to the same backend.
one API, many frontends. the engine doesn't care how you feed it markdown
github.com/fberrez/blur...
blurt.sh
#OpenSource #IndieDev #FOSS #SelfHosted #buildinpublic
one markdown file. six platforms. bluesky, mastodon, linkedin, medium, dev.to, substack.
write once, blurt everywhere. no copy-paste. no six browser tabs. no forgetting which platform you didn't post to yet
github.com/fberrez/blurt.sh
#OpenSource #IndieDev #FOSS #SelfHosted
happy friday. wrote about something that's been bugging me: why is your social publishing history trapped in someone else's postgres?
your posts should be files. grep works. git works. cp works.
blurt.sh/blog/why-your-social-posts-should-be-files
#ai #webdev #indiedev
you write a great post. then spend 20 min reformatting it for 6 platforms. copy-paste, resize images, fix char limits.
then pay $29/month for the privilege of scheduling it.
blurt fixes this. one markdown file. all platforms. files you own.
blurt.sh
#buildinpublic #webdev #indiedev
shipped the blurt.sh landing page in one afternoon:
express server (60 lines)
resend for waitlist emails
plausible for analytics
railway deploys from git push
nixpacks auto-detects node
the whole site is one html file + one js file.
blurt.sh
#buildinpublic #webdev #indiedev
first post going out from blurt.sh โ my own publishing queue that reads markdown files and blasts them to every platform at once
just a proof of concept but it works. that's all that matters
#ai #webdev #indiedev #buildinpublic
first post going out from blurt.sh โ my own publishing queue that reads markdown files and blasts them to every platform at once
just a proof of concept but it works. that's all that matters
#ai #webdev #indiedev #buildinpublic
i've been running a personal social queue script for months. markdown file in a folder โ published to bluesky, mastodon, linkedin.
today it stops being a script and becomes a real product
github.com/fberrez/blurt.sh
#OpenSource #IndieDev #FOSS #SelfHosted
yes, planned and post with blurt
thanks! i wanted to self-host on a vps with no interface โ just an editor and scp. your posts are markdown files, you own them, and if a platform dies tomorrow your content is still there. no export needed because there was never an import.
redesigned blurt.sh from soft gradients to brutalist terminal aesthetic.
sometimes a landing page just needs to look like it means business.
#ai #webdev #indiedev #buildinpublic #social #landingpage #design