hibira-io/hibira
Hibira realtime for AI coding agents: the Hibira MCP server plus skills for wiring channels, push notifications, AI streaming, human approvals, waiting rooms and the Chat API into your app, adding the Live Chat widget and knowledge base, and asking a Gaya panel for a second opinion.
Ask a person to approve an AI agent's or workflow's action through Hibira, either with the MCP request_approval tool, the signed approvals HTTP API, or the @hibira-io/approvals live inbox. Use for human-in-the-loop flows, tool-call approval, refunds, deploys or anything an agent should not do alone.
Stream Vercel AI SDK chat answers over Hibira channels with @hibira-io/ai-sdk so they survive reloads and dropped connections and reach every tab. Use when building a useChat UI, resumable AI chat, background generation, or streaming an agent's progress to a page.
Add in-app chat with stored history using the Hibira Chat API (beta). Use when building one-to-one or group messaging, support chat, unread counts, read receipts, typing indicators or push for offline users on top of Hibira, or when testing conversations with the MCP chat tools.
Get a second opinion from a group of AI personas with different points of view through the Gaya MCP server (gaya.hibira.io), and bring back their verdict. Use when the user asks what other people would think, wants a second opinion, a debate, pros and cons from several sides, or mentions Gaya or asking a group.
Put work in progress (landing page copy, a product or feature name, pricing, an onboarding flow, a launch post, a plan or an RFC summary) in front of a Gaya panel of AI personas, then turn their verdict into concrete edits. Use when the user asks how their copy, naming, pricing or plan will land with customers, wants a panel review or audience reaction, or asks Gaya to review something in the project.
How and when to use the Hibira MCP server (hibira.io/mcp) safely. Use when the task needs the user's real Hibira account, such as listing or creating apps, reading usage, sending a test event, watching the debug console, reading channels and presence members, configuring webhooks, rotating an app secret, deleting an app, publishing events, sending push notifications, asking a person for approval running a waiting room or testing Chat API conversations.
Fill a Hibira Live Chat knowledge base (what the AI assistant answers visitors from) from the business's own FAQ, help pages, policies, docs or product data, as a JSON file the user imports in one click. Use when the user wants to import, write, update or clean up Live Chat knowledge base entries, FAQ answers or the AI assistant's sources.
Connect a business's own admin panel or back office to Hibira Live Chat (chat.hibira.io) single sign-on, so its staff open the Live Chat inbox from it without a separate login. Uses the hibira-live-chat MCP server to read the workspace's setup, write the signing code for the project's stack and check the tokens it makes. Use when the user mentions Hibira Live Chat SSO, agent sign-in, or opening the Live Chat inbox from their admin.
Add the Hibira Live Chat widget (chat.hibira.io) to a website or web app, in any framework, so visitors can chat with the business and its AI assistant. Use when the user wants a live chat, support chat or chat bubble on their site with Hibira Live Chat, an Intercom, Crisp or tawk.to alternative, or wants to open the chat from their own button.
Move an existing Pusher Channels or Pusher Beams integration to Hibira. Use when a project already uses pusher-js, Laravel Echo with the pusher broadcaster, a Pusher server SDK, Beams push notifications, or Pusher webhooks, and the user wants to switch to Hibira.
Send push notifications to iOS, Android and browsers with Hibira Push (Beams-compatible). Use when adding device registration, interests, authenticated users, a service worker for Web Push, or sending notifications from a backend or agent.
Add Hibira realtime channels (WebSockets, Pusher protocol) to a web, mobile or backend project. Use when building live updates, chat, notifications in the page, online counts, presence, collaborative features or dashboards with Hibira, or when choosing between public, private, presence and large presence channels.
Put a Hibira virtual waiting room (queue) in front of a ticket drop, flash sale, launch or any page that would fall over if everyone arrived at once. Use when the user wants a queue, waiting room, Queue-it alternative, traffic surge or bot-rush protection, or wants to create, open, pause, close (sold out), post a notice on, or let people in from a waiting room.