Hibira for AI coding agents: the Hibira MCP server plus skills that teach your agent to wire Hibira realtime channels, push notifications, AI streaming, human approvals, in-app chat (Chat API) and virtual waiting rooms into your app; the Hibira Live Chat MCP server and skills for the chat widget, its knowledge base and single sign-on; and the Gaya MCP server for a second opinion from a group of AI personas.
| Client | Skills | MCP | How |
|---|---|---|---|
| Claude Code | ✅ | ✅ | Marketplace |
| Codex CLI | ✅ | ✅ | Marketplace |
| GitHub Copilot CLI | ✅ | ✅ | Marketplace |
| Gemini CLI | ✅ | ✅ | Extension |
| Cursor | ✅ | ✅ | Plugin or one click |
| VS Code (Copilot Chat) | ✅ | ✅ | Plugin or one click |
| OpenCode | ✅ | ✅ | Config |
| Zed | ✅ | ✅ | Settings |
| Windsurf, Cline, Kilo, Amp, Continue, … | ✅ | ✅ | npx skills + MCP URL |
| Claude.ai, ChatGPT | — | ✅ | Custom connector |
The MCP server signs in with OAuth. There is no API key to paste: the first Hibira tool call (or the client's MCP login command) opens a Hibira consent page, where you choose read only or read and write, and which apps the agent may use.
claude plugin marketplace add hibira-io/agent-plugin
claude plugin install hibira@hibiraThen run /mcp, pick hibira and sign in.
codex plugin marketplace add hibira-io/agent-plugin
codex plugin add hibira@hibira
codex mcp login hibiraOr run codex, type /plugins and install Hibira from there.
copilot plugin marketplace add hibira-io/agent-plugin
copilot plugin install hibira@hibiragemini extensions install https://github.com/hibira-io/agent-pluginThen /mcp auth hibira inside Gemini CLI.
Whole plugin (skills and MCP):
git clone https://github.com/hibira-io/agent-plugin.git ~/.cursor/plugins/local/hibiraand restart Cursor. MCP only: click Add to Cursor above, or add to .cursor/mcp.json:
{ "mcpServers": { "hibira": { "url": "https://hibira.io/mcp" } } }Whole plugin: clone this repository, open the Chat view, go to Plugins and add the folder. MCP only: click Install in VS Code above, or add to .vscode/mcp.json:
{ "servers": { "hibira": { "type": "http", "url": "https://hibira.io/mcp" } } }npx skills add hibira-io/agent-plugin -a opencodeand in opencode.json:
{ "mcp": { "hibira": { "type": "remote", "url": "https://hibira.io/mcp" } } }Then opencode mcp auth hibira.
Zed connects to remote MCP servers itself and signs in with OAuth. Open Settings → AI → MCP Servers → Add Server, or add this to settings.json:
{
"context_servers": {
"hibira": { "url": "https://hibira.io/mcp" }
}
}Then press Authenticate next to hibira in the Agent Panel settings. To use a personal access token instead of OAuth, add "headers": { "Authorization": "Bearer hkb_pat_..." }. Add the skills with npx skills add hibira-io/agent-plugin.
Any agent that reads SKILL.md folders can take the skills with skills, and any MCP client can use the server URL:
npx skills add hibira-io/agent-plugin # add -a <agent> for one client, -g for global
npx add-mcp https://hibira.io/mcpClients that read the Agent Plugins manifest (plugin.json, mcp.json) can load a clone of this repository directly.
MCP servers
hibira(https://hibira.io/mcp): list and create apps, read usage, get the setup guide for your SDK with your app's values filled in, send a test event and watch the debug console, see who is on which channel, configure and test webhooks, rotate a secret or delete an app (each only after you confirm the app's name), publish events, send push notifications, ask a person for approval, and run waiting rooms (create, open, pause, close, admit).hibira-live-chat(https://chat.hibira.io/mcp): for Hibira Live Chat owners and admins. Read the workspace's single sign-on setup, get the signing code for your stack with your workspace filled in, check the tokens your code signs (without signing anyone in), list agents and turn on "only single sign-on". It never sees your SSO secret.gaya(https://gaya.hibira.io/mcp): ask a Gaya group of AI personas a question and get their verdict back, then follow up in the room. Rooms use your own Gaya account's AI replies.
Each server signs in separately, the first time you use it.
Skills
| Skill | Use it for |
|---|---|
get-started |
First run: sign in, pick or create an app, send a first test event |
hibira-mcp-usage |
When and how to call the MCP tools safely |
realtime-integration |
Channels in web, mobile and backend projects (pusher-js, Laravel, Flutter, server SDKs) |
migrate-from-pusher |
Moving a Pusher Channels or Beams project to Hibira |
push-notifications |
Hibira Push for iOS, Android and browsers |
ai-streaming |
Resumable Vercel AI SDK chat with @hibira-io/ai-sdk |
agent-approvals |
Human-in-the-loop approvals for agents and workflows |
approval-before-risky-actions |
A second person's approval before the agent itself deletes files, force-pushes, deploys, runs terraform apply, publishes or writes to a database; what to do when the approval hook blocks a command |
chat-api |
In-app chat with stored history, unread counts and read receipts (Chat API, beta) |
waiting-room |
A virtual waiting room (queue) in front of a ticket drop or flash sale, in any framework |
livechat-sso |
Staff open the Hibira Live Chat inbox from your own admin panel (single sign-on) |
livechat-widget |
The Hibira Live Chat widget on your site, in any framework, opened from your own buttons |
livechat-knowledge |
A Live Chat knowledge base file written from your FAQ and help pages, imported in one click |
gaya-ask-group |
A second opinion from a Gaya group of AI personas, with the verdict and room link |
gaya-review |
A Gaya panel's reaction to your copy, naming, pricing or plan, turned into edits |
Try: "Add live order updates to this app with Hibira", "Move this project from Pusher to Hibira" "Put a waiting room in front of our ticket drop page" "Connect our admin panel to Hibira Live Chat single sign-on", "Add Hibira Live Chat to this site and fill its knowledge base from our FAQ" or "Ask Gaya which of these two headlines works better".
For store and event teams
A second plugin in this marketplace, hibira-merchant-ops (plugins/merchant-ops), is for the people who run the sale rather than build the site: a sale-day runbook (waiting room setup, the live panel, rate changes, notices, sold out, the Live Chat queue) and a daily Live Chat support digest as a sheet. Install it with claude plugin install hibira-merchant-ops@hibira.
Approval before risky commands
hibira-approval-hooks (plugins/approval-hooks) adds a hook to Claude Code, Codex and Cursor: rm -rf, git push --force, deploys, terraform apply, package publishing and database writes wait until someone in your Hibira Approvals workspace approves them on their phone; everything else runs as usual. Connect once with npx -y @hibira-io/mcp-approval-gate login --label "coding agent", then claude plugin install hibira-approval-hooks@hibira.
No plugin? Paste the short rules snippet from hibira.io/mcp-server into CLAUDE.md, AGENTS.md or a Cursor rule.
| Path | For |
|---|---|
skills/ |
The skills, shared by every client |
plugins/merchant-ops/ |
The hibira-merchant-ops plugin (its own manifest, MCP servers, skills and commands; versioned separately) |
plugins/approval-hooks/ |
The hibira-approval-hooks plugin: hook configs only (hooks/hooks.json for Claude Code and Codex, hooks/cursor.json for Cursor) that run npx @hibira-io/mcp-approval-gate hook; versioned separately |
.mcp.json |
MCP server (Claude Code, Codex, Cursor, Copilot, VS Code) |
.claude-plugin/ |
Claude Code plugin and marketplace (also read by Copilot CLI and VS Code) |
.codex-plugin/, .agents/plugins/ |
Codex plugin and marketplace |
.cursor-plugin/ |
Cursor plugin |
gemini-extension.json |
Gemini CLI extension |
plugin.json, mcp.json |
Agent Plugins manifest |
openai/submission.json |
ChatGPT plugin directory review data (test cases, release notes, translations) |
lobehub/lhm.plugin.json |
LobeHub MCP marketplace listing (npx -y @lobehub/market-cli plugin publish https://github.com/hibira-io/agent-plugin --dir lobehub) |
The check workflow (.github/workflows/check.yml) checks on every push that each manifest carries the same version and MCP URLs (the merchant ops and approval hooks plugins are checked against their own versions), and validates every plugin. The repo ships no script files, because the Claude plugin directory refuses them from publishers that are not Verified.
For the ChatGPT plugin directory, the same workflow builds hibira-chatgpt.zip and attaches it to the run as an artifact (run it by hand from the Actions tab to set a demo video URL): the Codex manifest plus openai/submission.json, the hibira MCP server only (the directory takes one server per plugin) and every skill except the Live Chat and Gaya ones. Upload it at platform.openai.com/plugins.
MIT
Hibira 的 AI 編程助手外掛:接上 Hibira MCP 伺服器(OAuth 登入,不需 API key),並附 15 個技能,讓助手能在你的專案裡接上即時頻道、推播、AI 串流、人工審核、聊天(Chat API)與排隊等候室(建立、開放、暫停、售罄、放行,並在任何框架裡驗證 pass),也能協助從 Pusher 遷移。另含 Hibira 即時客服的 MCP 伺服器(https://chat.hibira.io/mcp),可幫你把自家後台接上即時客服的單一登入,讓客服從後台直接打開收件匣;它看不到你的 SSO 密鑰。新技能可把即時客服小工具裝到任何網站,並把你的 FAQ 和說明頁整理成知識庫 JSON 檔一鍵匯入。也含 Gaya 的 MCP 伺服器(https://gaya.hibira.io/mcp),可請一群 AI 角色討論問題或評估文案、命名與定價,帶回結論和房間連結。另有 hibira-approval-hooks 外掛:讓 Claude Code、Codex、Cursor 執行 rm -rf、git push --force、部署、terraform apply、發佈套件、資料庫寫入等不可逆指令前,先送到 Hibira Approvals 工作區等另一個人在手機上核准;新技能 approval-before-risky-actions 教助手何時該先請人核准、被擋下時該怎麼做。沒有外掛的話,可到 hibira.io/mcp-server 複製一段規則貼進 CLAUDE.md、AGENTS.md 或 Cursor 規則。支援 Claude Code、Codex、Copilot CLI、Gemini CLI、Cursor、VS Code、OpenCode、Zed(在 context_servers 填 MCP 網址即可,Zed 會用 OAuth 登入),其他工具可用 npx skills add hibira-io/agent-plugin 加上 MCP 網址 https://hibira.io/mcp。ChatGPT 外掛目錄的上傳用 ZIP 由 GitHub Actions 的 check 工作流程產生(只含 hibira 一個 MCP 伺服器)。lobehub/lhm.plugin.json 是 LobeHub MCP 市集的上架資料。