Zebra BI

com.zebrabi由 zebrabi.com 发布官方发布者v1.0.2更新于 Nov 7, 2026

Draw business data as interactive IBCS-style Zebra BI charts and tables.

已验证Streamable HTTP可网页运行数据与分析媒体与设计

概览

AI 生成的概览

Zebra BI MCP 把汇总后的业务数据绘制成可交互的 IBCS 风格图表和表格，直接显示在对话中并呈现差异。

可以做什么
  • 根据汇总数据绘图：传入实际值及上年、计划或预测数据，得到可交互的 IBCS 风格 Zebra BI 图表；不支持 MCP Apps 的宿主只显示文字摘要。
  • 解释差异：将实际值与上年、上月、计划或预测进行对比。
  • 生成数据故事：把数据集整理成一条核心信息、三到五条支撑发现，并为每条配上图表。
  • 查找并记住数据源，例如本地 CSV 或 Excel、SharePoint 或 OneDrive 中的 Excel，以及 Power BI 语义模型。
  • 按需产出可分享文件：A4 PDF、Claude artifact 页面，或含实时 Zebra BI 视觉对象的 PowerPoint 演示文稿与 Excel 工作簿。
适用场景
适合希望在 AI 对话中以 IBCS 图表呈现业务数据、差异分析和控制师风格数据故事，并偶尔导出为 PDF、PowerPoint 或 Excel 分享的场景。
运行要求
远程 MCP 端点 mcp.zebrabi.com，连接器本身无需安装包或本地运行时。MCP 需要登录，故事脚本另需通过 OAuth 流程登录并在本地保存令牌。PDF、artifact 和 Office 技能需要 Claude Code、python3（仅标准库）以及 Chromium 内核浏览器。实时 Office 视觉对象需要安装 Zebra BI Charts 或 Tables 加载项并具备相应许可。
安装前请注意
每次绘图都会把类别与期间标签及汇总数值发送给 Zebra BI，因此客户名、员工名等标签会离开本机；渲染失败时会把发送的参数一并上报至 Zebra 的错误监控。登录令牌保存在本地 auth.json。文件及 SharePoint 或 Power BI 数据源的完整副本会写入工作目录下的 .zebra/，该目录默认不会被 git 忽略。artifact 页面会发布到 claude.ai，品牌网页字体可能让字体主机看到读者地址。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Zebra BI，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.zebrabi%2Fzebra-bi/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "zebra-bi": {
      "type": "http",
      "url": "https://mcp.zebrabi.com/mcp"
    }
  }
}

README

Zebra BI plugin

The Zebra BI plugin bundles the Zebra BI MCP connector with the skills that put it to work, in one install for AI assistants such as Claude, ChatGPT and GitHub Copilot Chat, and for coding agents such as Claude Code, Codex and Copilot CLI. The connector draws your business data as interactive IBCS-style charts and tables, inline in the conversation. The skills tell your assistant when to use it and how, for variances, data stories and files to share. The plugin comes in Claude's format and in Agent Plugins, the format VS Code, Copilot CLI, ChatGPT and Codex read. Any other MCP client can connect to the Zebra BI MCP on its own.

The MCP has one tool, render_visual. Your assistant or agent sends it aggregated figures, such as actuals with a previous year, plan or forecast, and Zebra BI draws the variances. Hosts that support MCP Apps show the interactive visual; the others show a text summary of what was drawn.

The skills add three things on top of the tool:

  1. Charts and variances. When and how to show business figures as a Zebra BI visual, and how to explain actuals against previous year, previous month, plan or forecast.
  2. Data stories. Hand your assistant or agent a dataset and get back the story a controller would tell: one key message, the three to five findings that prove it, and a Zebra BI chart for each one. Every number comes from a computation on your data, and the story never adds a cause the data does not show.
  3. Files to share. One A4 PDF of a story, or a PowerPoint deck and an Excel workbook with live Zebra BI for Office visuals, in your company's brand. Made only when someone asks for a file.

Skills

SkillWhat it does
chart-from-dataWhen to show findings as a visual, and how to shape the data for render_visual.
variance-analysisHow to explain actuals against previous year, previous month, plan or forecast, and show the variances.
data-sourceFinds a dataset (local CSV or Excel, Excel in SharePoint or OneDrive, a Power BI semantic model) and remembers it in .zebra/sources/, so the file, sheet, date format or query is never asked twice.
data-storyAnalyses the data and tells an IBCS story in the conversation, with a Zebra BI chart for every supporting message. In Claude Code it also saves the story in .zebra/stories/.
story-pdfTurns a saved story into one A4 PDF: the key message and KPIs, each supporting message with its chart, page numbers. Chart labels and values stay text. Claude Code only.
story-artifactPublishes a saved story as one shareable Claude artifact page: the key message and KPIs, each supporting message with its Zebra BI chart. Charts are pictures of the Zebra BI charts, or live charts with hover on request. A plain artifact page, since the Dashboard artifact type cannot carry Zebra BI charts. Claude Code only.
story-officeWrites a saved story as a PowerPoint deck and an Excel workbook. Each chart is a live Zebra BI for Office visual where the Charts or Tables add-in is installed, and a picture of the chart for everyone else. Claude Code only.
story-brandSets the look and voice of story files: colours, fonts, logo, credit line, your PowerPoint template and its layouts, and the tone of the writing. The charts keep their IBCS colours whatever the brand.

In Claude Code the skills run as /zebra-bi:<skill>, for example:

/zebra-bi:data-story ~/Downloads/sales.csv      # tell the story in the conversation/zebra-bi:story-pdf sales-2026-q3               # one shareable PDF/zebra-bi:story-artifact sales-2026-q3          # one shareable artifact page/zebra-bi:story-office sales-2026-q3            # PowerPoint deck and Excel workbook/zebra-bi:story-brand                           # dress story files in your company's brand

Install

[Install the MCP in VS Code] [Install the MCP in VS Code Insiders]

The MCP URL is https://mcp.zebrabi.com.

  1. Claude Code: /plugin marketplace add zebrabi/zebra-bi, then /plugin install zebra-bi@zebrabi. Installs the MCP and the skills.
  2. VS Code: run "Chat: Install Plugin From Source" and enter https://github.com/zebrabi/zebra-bi. Installs the MCP and the skills. The VS Code buttons above install the MCP only.
  3. claude.ai, Claude Desktop and Cowork: add the MCP URL as a custom connector under Settings > Connectors. This adds the MCP only.
  4. ChatGPT: in developer mode, add the MCP URL with "Add custom MCP server". This adds the MCP only.

Where the charts draw. Claude Desktop chat and claude.ai show the visual inline. The Claude Code desktop tab draws it only through the MCP added as a connector in the Claude Desktop app (step 3). The plugin's own copy, which Claude Code loads too, returns the chart's data, so the skills use the connector when both are there. The Claude Code terminal cannot show MCP Apps and prints the chart data instead.

Data stories and files. data-story works wherever the MCP is connected. The .zebra/ folder, the PDF, the artifact page and the Office files need Claude Code, python3 (standard library only) and Google Chrome, Microsoft Edge or Chromium. In Claude chat or Cowork, story-pdf, story-artifact and story-office hand over the story as JSON instead of building a file. Readers need the Zebra BI Charts or Tables for Office add-in, and its licence, to see the Office visuals live.

What this plugin sends and runs

  • The MCP. The skills call render_visual once per chart. Each call sends the chart's arguments: the category and period labels, the aggregated values per scenario and the titles. The labels are your data's own values, so a chart by customer or employee sends those names; leave out anything that should not leave your machine. Each skill says so in one line before its first chart. The source file is never sent. A chart that fails to render is reported to Zebra's error monitoring together with the arguments that were sent.
  • story-pdf, story-artifact and story-office. Their Python scripts send the same chart arguments to the same MCP over HTTPS and print Sending <n> chart(s) to <endpoint> first. A chart whose arguments did not change is reused from .zebra/stories/<story>/visuals/. Once a day they download the chart renderer (the ui:// page render_visual names in tools/list) and cache it in $CLAUDE_PLUGIN_DATA, or in ~/.cache/zebra-bi when that is not set. A renderer or chart fetched from another MCP address is never reused. The plugin sends no telemetry.
  • The artifact page. story-artifact publishes the page and a picture of each chart to claude.ai as a private artifact, which its owner shares from the page's Share menu. It holds the story's aggregated numbers, not the source data. With --live it also carries the Zebra BI renderer, which draws the charts in each reader's browser.
  • A local browser. story-pdf, story-artifact, story-office and the story-brand preview start Chrome, Edge or Chromium headless, with a throwaway profile and its background traffic (updates, sync, metrics, safe-browsing lists) turned off. The scripts drive it over a private pipe that no other program can reach; on Windows over a remote-debugging port bound to 127.0.0.1. The browser closes when the file is done.
  • A web font, if a brand sets one. With fonts.web_css set, the headless browser loads that stylesheet while it builds the PDF, and an artifact page loads it in every reader's browser, so the font host (for an artifact, always Google Fonts) sees each reader's address. The default brand sets none.
  • What is written. Files under .zebra/ in your working folder (sources, stories, brand, and the PDF, PowerPoint and Excel files) and the renderer cache. A source read from SharePoint or a Power BI model keeps a full copy of the sheet or query result in .zebra/sources/. Nothing keeps .zebra/ out of git, so add it to .gitignore when the working folder is a repository and the data is confidential.
  • Sign-in. The MCP asks for sign-in, and the scripts sign in on their own, apart from the connector: python3 -I scripts/story.py sign-in opens the Zebra BI sign-in page in your browser (OAuth with PKCE, answered on a 127.0.0.1 port) and keeps the token in auth.json next to the renderer cache, readable only by you. Sign-in stops when the MCP's sign-in metadata names another server. The token is sent only to the MCP it was issued for, and to its sign-in server to refresh or revoke it. Without a valid token a build stops with Zebra BI needs sign-in and writes no file. story.py sign-out revokes and forgets every kept sign-in, an older MCP address included.

Help

Repository layout

PathRead by
.claude-plugin/plugin.json, .mcp.jsonClaude Code, claude.ai, Claude Desktop, Cowork, the Anthropic directory
.claude-plugin/marketplace.jsonClaude Code and Copilot marketplaces
plugin.json, mcp.jsonAgent Plugins 1.0: VS Code, Copilot CLI, ChatGPT and Codex
skills/Hosts that install the plugin
scripts/, assets/The story skills in Claude Code: profiling, PDF and Office builds, the brand default and the page template

CONTRIBUTING.md covers the internals and how to run the checks.

Versions

The plugin and the MCP carry separate versions. Every plugin release bumps version in .claude-plugin/plugin.json and plugin.json, because Claude Code updates an install only when version changes and third-party marketplaces do not update plugins automatically; the release workflow makes that bump, and CI checks the two match and that every manifest carries the same MCP URL. The MCP server, its version and its MCP Registry entry are released from its own repository.

Releases are cut from develop; CONTRIBUTING.md covers how.

License

Apache-2.0

来源：README.md，提交 7654ae8

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

3
  1. v1.0.2最新Nov 5, 2026
  2. v1.0.1Nov 4, 2026
  3. v1.0.0Nov 3, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证不适用

    托管服务按其提供方的条款使用，因此这里不要求许可证。此检查项不计入百分比。