No description
81d43c30f4
The public REST API accepted inline post media as a free-form array and stored it verbatim, so a client could create/update a post whose media was a bare external URL we never hosted. Publishing then depended on that third-party URL staying alive — when it 404'd (e.g. an image proxy), the post failed across platforms (Facebook 'unsupported media type', X 'HTTP 404', Instagram 'could not fetch media'). Inline media URLs on create/update now go through the same download + MIME- validate + host path as the attach-from-url endpoint (MediaAttacher), so the stored media always points at our own storage. Items already hosted (carrying a path) pass through untouched. If any URL can't be fetched the request is rejected with 422 and nothing is persisted, so a post is never created with broken media. MCP and the web flow were already safe and are unchanged. - MediaAttacher: extract fetchToWorkspace() + add resolveInlineMedia() - Post::allowedMediaTypesFor() so the create flow can compute allowed types without a persisted post - API Store/UpdatePostRequest: media.* item rules (mirroring the web; prevents validated() from stripping hosted-item keys) - PostController store()/update(): host external media before persisting |
||
|---|---|---|
| .claude | ||
| .cursor/rules | ||
| .github | ||
| app | ||
| bootstrap | ||
| config | ||
| database | ||
| docker | ||
| lang | ||
| maizzle | ||
| public | ||
| releases | ||
| resources | ||
| routes | ||
| storage | ||
| stubs | ||
| templates | ||
| tests | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.ci | ||
| .env.example | ||
| .env.testing | ||
| .gitattributes | ||
| .gitignore | ||
| .mcp.json | ||
| .prettierignore | ||
| .prettierrc | ||
| artisan | ||
| boost.json | ||
| Caddyfile | ||
| CLAUDE.md | ||
| components.json | ||
| compose.override.yaml.example | ||
| compose.prod.yaml | ||
| compose.yaml | ||
| composer.json | ||
| composer.lock | ||
| eslint.config.js | ||
| GEMINI.md | ||
| LICENSE.md | ||
| package-lock.json | ||
| package.json | ||
| phpunit.xml | ||
| pint.json | ||
| README.md | ||
| tsconfig.json | ||
| vite.config.ts | ||
Run your whole social presence from one calendar
An open-source social media scheduler with an AI copilot, native publishing to 12 networks,
and an MCP server so your AI assistant can post for you. Self-host it, or skip the setup on cloud.
Try on Cloud • Documentation • Community
What you get
| 📅 One calendar, every network | Plan a month at a glance, drag any post to a new slot, and publish natively to 12 platforms. No redirects, no "finish in the mobile app." |
| ✨ An AI copilot that knows your brand | Captions, hooks, full drafts, and multi-slide carousels in your tone, voice, and colors. It reads your brand profile on every generation. |
| 🤖 Built for AI agents | A first-class MCP server and REST API. Claude, Cursor, ChatGPT, or your own scripts can draft, schedule, and publish for you. |
| ⚙️ Automations that run themselves | A visual workflow builder: triggers, conditions, RSS, webhooks, and AI generation, all server-side. Set it once, let it post. |
| 🗂️ Made for many clients | Workspaces, roles, and approval flows so an agency or freelancer can run a roster of brands without the spreadsheets. |
Features
| Visual calendar | Month, week, and day views. Drag and drop to reschedule across networks. |
| Multi-platform composer | Write once, then tailor the preview per network in parallel. |
| AI generate & review | Draft from a prompt, get inline feedback before you publish. |
| AI carousel builder | Prompt to a multi-slide carousel with images, on-brand. |
| Brand profile | Tone, voice, language, and colors applied to every AI call. |
| Automations | Schedule / RSS triggers, conditions, publish steps, and webhooks. |
| Asset library | Reusable workspace media, plus Unsplash and Giphy search built in. |
| Signatures & labels | Reusable hashtag and CTA blocks, color-coded post tags. |
| Team collaboration | Owner / Admin / Member roles, comments with @mentions on drafts. |
| Workspaces | Isolate each brand, client, or project in its own space. |
| REST API + MCP | Full programmatic control; AI assistants integrate natively. |
| Native analytics | Per-account reach and engagement across every connected platform. |
| Multi-language | English, Spanish, and Portuguese. |
Supported platforms
Posts publish natively through each platform's official API.
 |
 |
 |
 X (Twitter) |
 TikTok |
 YouTube |
 |
 Threads |
 Bluesky |
 Mastodon |
 Telegram |
 Discord |
Get started
| ☁️ Cloud | The fastest way in. We host, update, and scale it for you. Start at trypost.it → |
| 🛠️ Self-host | Free forever, your servers, your data. Installation guide → |
| 🤖 Drive it with AI | Connect Claude, Cursor, or ChatGPT over MCP. MCP setup → |
Own your stack
TryPost is open source on purpose. Self-host it and your posts, drafts, and metrics stay on your infrastructure, under a license that is yours to keep. No seat tax, no feature gates, no vendor deciding when to lock you out. Read every line, fork it, and ship it. When you would rather not run servers, the same product is one click away on cloud.
Contributing
Contributions of any size are welcome. Pick an issue, say hi in Discussions, or open a PR with what you would like to see.
Short on time? A star is the most valuable thing you can give. It helps more people find the project.
License
GNU Affero General Public License v3.0. Use, modify, fork, self-host, and redistribute, including commercially. If you run a modified version as a network service, make your changes available to its users (AGPL §13).
Built in the open. Star TryPost on GitHub and tell a friend.
Star History