Beezi Analytics Plugin
beezi-analytics is a small, read-only Beezi plugin for Claude Code, Codex and GitHub Copilot. It shows your personal Beezi usage summary inside your coding tool: spend, sessions, top model, a status, and up to three recommendations for the last 7 or 30 days.
The plugin has no hooks, no scripts, and no local code. It connects to one remote server, the Beezi MCP server, and you sign in with your Beezi account in the browser. It does not record your sessions and sends nothing from your conversations. See Privacy & What It Connects To for details.
1. Where the Numbers Come From
The plugin reads the analytics Beezi already has for your account. Beezi records sessions through its session-tracking plugins for Claude Code, Codex and GitHub Copilot, installed from the Beezi portal. If Beezi has no sessions for you yet, the summary says there is not enough activity.
If you already use Beezi's session-tracking plugin in this tool, you don't need this one: it shows the same summary.
2. Requirements
- A Beezi account. Everything the plugin reads is read as you, from your default Beezi workspace.
- Claude Code, Codex or GitHub Copilot with plugin support.
There is nothing else to install. The plugin does not need Node.js and has no build step.
3. Claude Code
Install
Add Beezi's marketplace, then install the plugin:
/plugin marketplace add Beezi-AI/beezi-claude-plugin
/plugin install beezi-analytics@beezi
If you have already added Beezi's marketplace, skip the first command. The marketplace also lists Beezi's session-tracking plugin, beezi, which shows the same summary; you need only one of them.
Sign In
Run /mcp, choose the beezi server, then select Authenticate. A browser window opens for your Beezi sign-in.
Until you have signed in, the summary replies with the same instruction: Sign in to Beezi first: run /mcp, choose the beezi server, then Authenticate.
Usage
/beezi-analytics:analytics
/beezi-analytics:analytics 30d
/beezi-analytics:about
analyticsprints your summary. With no period, or any value other than7dor30d, it uses the last 7 days. You can also ask Claude for your Beezi analytics in plain words.aboutexplains what the plugin does and where the numbers come from.
The key numbers cover all your coding agents. The recommendations cover Claude Code. To get recommendations for every coding agent you use, ask for your Beezi analytics for all agents.
4. Codex
Install
Add Beezi's marketplace, then install the plugin:
codex plugin marketplace add Beezi-AI/beezi-codex-plugin
codex plugin add beezi-analytics@beezi
Start a new Codex thread after installing.
On Codex 0.167, the plugin installs from Beezi's marketplace but does not connect yet. That version ignores an MCP server whose entry carries the sign-in settings that OpenAI's plugin directory asks for, and this plugin declares them.
Sign In
The first time you ask for your analytics, Codex asks you to connect the beezi_analytics MCP server. Follow the browser sign-in with your Beezi account. You do not type anything in the terminal.
Usage
Ask in plain words:
Show my Beezi analytics for the last 7 daysShow my Beezi analytics for the last 30 daysWhat does the Beezi analytics plugin do?
You can also ask for the analytics or the about skill by name. With no period named, the summary covers the last 7 days.
In Codex, the summary always covers every coding agent linked to your Beezi account, not Codex alone.
5. GitHub Copilot
Install
Add Beezi's marketplace, then install the plugin:
copilot plugin marketplace add Beezi-AI/beezi-copilot-plugin
copilot plugin install beezi-analytics@beezi-copilot
If you have already added Beezi's marketplace, skip the first command. The marketplace also lists Beezi's session-tracking plugin, beezi, which shows the same summary; you need only one of them.
Sign In
Run /mcp, choose the beezi server, then sign in. A browser window opens for your Beezi sign-in.
Until you have signed in, the summary replies with the same instruction: Sign in to Beezi first: run /mcp, choose the beezi server, then sign in.
Usage
/beezi-analytics
/beezi-analytics 30d
/beezi-about
/beezi-analyticsprints your summary. With no period, or any value other than7dor30d, it uses the last 7 days. You can also ask Copilot for your Beezi analytics in plain words./beezi-aboutexplains what the plugin does and where the numbers come from.
The key numbers cover all your coding agents. The recommendations cover GitHub Copilot. To get recommendations for every coding agent you use, ask for your Beezi analytics for all agents.
6. What the Summary Shows
- Status: 🟢 Healthy, 🔵 Keep monitoring, 🟣 Needs attention, or ⚪ Not enough data.
- Key numbers: a money line, sessions, top model and its share of tokens, and active days.
- Patterns: short observations about your usage, when Beezi has any.
- Recommendations: up to three, the most severe ones Beezi found, each with a link to read more when Beezi has one.
- Portal link: the last line links to your analytics in the Beezi portal.
The money line depends on how your usage is billed:
| Billing | Money line |
|---|---|
| API key | Your API spend |
| Subscription | Your usage at API prices and your share of the subscription |
| Both | Usage at API prices, subscription share, and the API-billed amount |
| Not reported | Usage at API prices, with a note that the billing source was not reported |
"Usage at API prices" is what your usage would cost at API list prices. It is not what you were billed.
Every figure, observation and recommendation comes from Beezi. The plugin's skill carries a fixed template and tells your model to copy Beezi's text into it as is, without calculating, rewording or adding advice of its own. Recommendations only suggest; the plugin never runs a command or changes a setting.
The summary always covers only you, whatever your role, and reads your default Beezi workspace. It cannot read another workspace by name. If you ask about someone else, the plugin replies with a short refusal and points you to the Beezi portal.
7. Privacy & What It Connects To
- One MCP server:
https://api.beezi.ai/api/mcp. Claude Code lists it asbeezi, Codex asbeezi_analytics, and GitHub Copilot asbeezi. - Agent header: Codex sends
X-Beezi-Agent: codexand GitHub Copilot sendsX-Beezi-Agent: copilotwith each request, so Beezi knows which tool the request comes from. All three plugins sendX-Beezi-Plugin: light, so Beezi offers them only the personal summary. - Sign-in: OAuth through
https://clerk.beezi.ai, in your browser. Claude Code, Codex or GitHub Copilot keeps the sign-in, as it does for any MCP server. The plugin has no credential store of its own. - What it sends: the request for your summary and its period, and the
X-Beezi-Plugin: lightheader. In Codex it also asks for all agents and sends theX-Beezi-Agent: codexheader. In GitHub Copilot it also sends theX-Beezi-Agent: copilotheader. Nothing from your prompts, your model's responses, your files or your session transcripts. - Read-only: every tool on the Beezi MCP server is read-only. The plugin can read only your personal summary.
- No local code: no hooks, no scripts, and no files written on your machine.
See the Beezi privacy policy and terms.
8. Availability
The plugin is free to install. The summary depends on your Beezi plan. If your plan does not include the personal analytics summary, the plugin tells you it is disabled for your plan. Check your plan in the Beezi portal or ask your workspace owner.
9. Troubleshooting
The Summary Asks You to Sign In
Problem: The reply is Sign in to Beezi first.
Solution: In Claude Code, run /mcp, choose the beezi server, then Authenticate. In GitHub Copilot, run /mcp, choose the beezi server, then sign in. In Codex, reconnect the beezi_analytics server when Codex asks, then try again. Sign in with the Beezi account whose analytics you want to see.
Codex Never Asks to Connect the Server
Problem: On Codex 0.167, the plugin is installed but its server never connects.
Solution: This is a known limitation of that Codex version with this plugin. See the note under Codex.
No beezi Server in Claude Code
Problem: Claude cannot find the Beezi tools, or /mcp does not list the beezi server.
Solution:
- Run
/pluginand check thatbeezi-analyticsis installed and enabled. - Restart Claude Code.
- Run
/mcpand sign in to thebeeziserver.
Not Enough Activity to Grade This Period
Problem: The status is ⚪ Not enough data.
Solution: Beezi has too little tracked activity for your account in this period. Try 30d. If Beezi has no sessions for you at all, ask your workspace owner how Beezi records sessions in your organization.
The Summary Is Disabled for Your Plan
Problem: The reply says the personal analytics summary is disabled for your Beezi plan.
Solution: The summary is not part of your current plan. Check your plan in the Beezi portal or ask your workspace owner.
The Summary Shows the Wrong Workspace
Problem: Your account belongs to several Beezi workspaces, and the summary reads a different one from the one you want.
Solution: This plugin always reads your default workspace. To see another workspace, open it in the Beezi portal.
Both Plugins Are Installed
Problem: You have beezi-analytics and Beezi's session-tracking plugin, beezi, in the same tool.
Solution: Uninstall beezi-analytics. The beezi plugin shows the same summary.
10. Getting Help
If you encounter issues not covered here:
- Support Email: hello@beezi.ai
- Contact form: https://beezi.ai/contact-us
When contacting support, include:
- Your coding tool and its version (Claude Code, Codex or GitHub Copilot)
- The command or prompt you ran, and its exact output
- Error messages or screenshots