solo-publisher

mcp
Security Audit
Warn
Health Warn
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Warn
  • process.env — Environment variable access in apps/backend/drizzle.config.ts
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Agent-native, self-hosted publishing studio for solo creators. Write in chat, publish everywhere, and own the stack.

README.md

English · Русский

Solo Publisher

Write in chat. Publish everywhere. Own the stack.

Write from Telegram or an MCP client such as Codex; Solo Publisher publishes to
your website, Telegram, X, Threads, YouTube Shorts and Instagram, schedules and
retries every destination independently, and collects the analytics back. One
owner, one server, no SaaS in the middle.

A live publication powered by Solo Publisher

Not a starter kit or a mockup. This is the complete publishing pipeline
running in production behind a real, daily-updated publication.

Install

Docker, and a domain whose DNS already points at this machine:

curl -fsSL https://raw.githubusercontent.com/alexgetmancom/solo-publisher/main/install.sh | sh -s -- publisher.example.com

It checks Docker and the DNS before touching anything, generates the secrets,
starts the stack, gets the TLS certificate, and prints your Command Center link
with its token. Run it again to update. → Install guide

Try it without installing

Needs Bun 1.3.14 and the native build prerequisites for
sharp:

bun install --frozen-lockfile
bun run demo

Public site at http://localhost:8788/, Command Center at
http://localhost:8788/command-center?token=dev — fixture content, no
credentials, Ctrl+C to stop.

Solo Publisher Command Center with text and video analytics

Docs

License

Apache License 2.0.

Reviews (0)

No results found