Shared workspace where teams work with agents together
Kollab is a shared workspace where AI agents become part of your team. Bots bring agents inside your IM like Slack without switching apps, Skills let anyone reuse your best workflows, Connectors link the tools you already use, and Memory keeps context alive across every project. No setup, no busywork.
YAN here, one of the makers behind Kollab. We built it so our team could stop bouncing between Slack, GitHub, Notion and half a dozen separate agent tools. One agent, sitting across every channel the team already lives in, with any MCP server wired behind it.
Here's how we use it ourselves. Kollab's hooked into our Slack and Telegram bots, with Notion MCP and GitHub MCP behind them. Inside our work group, anyone (devs or not) can ping the bot to look at code, review a feature, or file an issue. In the community group, users @Kollab to report bugs or ask how something works, and every message routes through Notion MCP straight onto our backend board. Feedback used to get lost in DMs; now it doesn't.
The piece we underestimated most is scheduled tasks. We thought we were shipping a digest job, but a scheduled task on Kollab is really a timed agent. The same cron can call any MCP tool, pull from the knowledge base, run as a specific agent role, and post back to any channel. Ours right now: one drafts a weekly changelog from GitHub issues, one cross-checks our status page against Sentry, one pings the on-call before standup. Same thing under the hood, totally different jobs on top.
When we need more than a quick answer, there's AgentCore. Long-running agent with its own filesystem and a browser built in. We've been using it to stand up small demo sites and internal tools instead of writing throwaway scripts. And since skills are just regular GitHub repos, anything the team keeps repeating turns into a skill the whole org can install by name. We're still early on this part, and it's probably where we'll end up finding the weirdest uses.
Question for PH: if you had one agent sitting across your team's channels with full MCP reach, what's the first scheduled task or skill you'd write? No idea what people will come up with. So far the answers have been all over the map, and two of them are already in our next release.
About Kollab on Product Hunt
“Shared workspace where teams work with agents together”
Kollab launched on Product Hunt on April 23rd, 2026 and earned 165 upvotes and 14 comments, earning #2 Product of the Day. Kollab is a shared workspace where AI agents become part of your team. Bots bring agents inside your IM like Slack without switching apps, Skills let anyone reuse your best workflows, Connectors link the tools you already use, and Memory keeps context alive across every project. No setup, no busywork.
On the analytics side, Kollab competes within Productivity, Artificial Intelligence and No-Code — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Kollab performed against the three products that launched closest to it on the same day.
Who hunted Kollab?
Kollab was hunted by Justin Jincaid. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Kollab including community comment highlights and product details, visit the product overview.
Justin Jincaid
Hey PH 👋
YAN here, one of the makers behind Kollab. We built it so our team could stop bouncing between Slack, GitHub, Notion and half a dozen separate agent tools. One agent, sitting across every channel the team already lives in, with any MCP server wired behind it.
Here's how we use it ourselves. Kollab's hooked into our Slack and Telegram bots, with Notion MCP and GitHub MCP behind them. Inside our work group, anyone (devs or not) can ping the bot to look at code, review a feature, or file an issue. In the community group, users @Kollab to report bugs or ask how something works, and every message routes through Notion MCP straight onto our backend board. Feedback used to get lost in DMs; now it doesn't.
The piece we underestimated most is scheduled tasks. We thought we were shipping a digest job, but a scheduled task on Kollab is really a timed agent. The same cron can call any MCP tool, pull from the knowledge base, run as a specific agent role, and post back to any channel. Ours right now: one drafts a weekly changelog from GitHub issues, one cross-checks our status page against Sentry, one pings the on-call before standup. Same thing under the hood, totally different jobs on top.
When we need more than a quick answer, there's AgentCore. Long-running agent with its own filesystem and a browser built in. We've been using it to stand up small demo sites and internal tools instead of writing throwaway scripts. And since skills are just regular GitHub repos, anything the team keeps repeating turns into a skill the whole org can install by name. We're still early on this part, and it's probably where we'll end up finding the weirdest uses.
Question for PH: if you had one agent sitting across your team's channels with full MCP reach, what's the first scheduled task or skill you'd write? No idea what people will come up with. So far the answers have been all over the map, and two of them are already in our next release.