可嵌入的浏览器聊天小部件，适用于llm_meta生态系统（客户端编排流程，三类MCP工具分类法）
概览
可嵌入的浏览器聊天小部件，适用于llm_meta生态系统。 浏览器负责编排。启动时，小部件读取你页面声明的工具以及主机发布的任何已知/mcp.json工具。当模型调用工具时，小部件运行它：无论是在页面本身，还是直接对MCP端点运行。只有聊天通过元服务器，通过SSE进行。 它作为一个自包含的ES模块中的自定义元素发布。同一文件在npm上对任何主机都有，也在Rails宝石中，其助手会为你提供。 设计、数据库迁移、ChatManager 或 PromptNavigator。该宝石只添加 Rails >= 8.0 作为运行时 dep——这样还没升级到 8.1 的主机可以在不升级 Rails 的情况下采用它——不使用 Rails 的主机也不需要 gem。 小部件是浏览器前端：需要有东西来回复聊天。一个选项是 ，一个存储提供者凭证并回流回响应的枢纽。另一个是 ，小工具直接与它通信，中间没有我们的服务器组件。
概述（AI 翻译）
可嵌入的浏览器聊天小部件，适用于llm_meta生态系统。
浏览器负责编排。启动时，小部件读取你的页面工具
宣告，以及你的主机发布的任何.well-known/mcp.json。当模型调用时
一个工具，小部件运行它：在页面本身，或对 MCP 端点运行
直接。只有聊天通过元服务器，通过SSE进行。
它作为一个自包含的ES模块中的自定义元素发布。同样的文件也在 NPM对任何主机都有，在Rails宝石中，助手会帮你提供。
不 Devise、数据库迁移、ChatManager或PromptNavigator。宝石只添加rails >= 8.0作为运行时DEP——这样还没升级到8.1的主机无需升级Rails即可采用——不使用Rails的主机也不需要宝石。
要求
小部件是浏览器前端：它需要有东西来回复聊天。一 选项是llm_meta_server，一个枢纽 持有提供者凭证并回流响应。另一个是an Ollama，小部件直接与它通信，没有我们的服务器组件 介于两者之间。
这些与工具来源是分开的。集线器也会注册MCP工具
本页由 AI 翻译，技术细节请以原文为准。
README
以下为原文 README 节选，完整内容请查看原文。
llm_meta_widget
Embeddable browser chat widget for the llm_meta ecosystem.
The browser does the orchestrating. At boot the widget reads the tools your page
declares and any .well-known/mcp.json your host publishes. When the model calls
a tool, the widget runs it: in the page itself, or against an MCP endpoint
directly. Only the chat goes through the meta-server, over SSE.
It ships as a custom element in one self-contained ES module. The same file is on npm for any host, and in a Rails gem whose helper serves it for you.
No Devise, DB migrations, ChatManager, or PromptNavigator. The gem adds only rails >= 8.0 as a runtime dep — so hosts that haven’t bumped to 8.1 can adopt it without a Rails upgrade — and hosts that do not use Rails do not need the gem.
Requirement
The widget is a browser front end: it needs something to answer the chat. One option is llm_meta_server, a hub that holds provider credentials and streams responses back. The other is an Ollama, which the widget talks to directly, with no server component of ours in between.
Those are separate from where tools come from. A hub also registers MCP tools
(Class 1 below), and you can point at one for tools while a local Ollama
answers the chat, or use no hub at all. Page actions and your own
.well-known/mcp.json never involve a hub either way.
Nothing else is required: no database, no migrations, no JavaScript build step, no Node at runtime.
| Requirement | Version | Needed when |
|---|---|---|
| A browser with custom elements + ES modules | any current | always |
| An llm_meta_server or an Ollama | any | always — something has to answer the chat |
Nothing is required of your server: the widget runs in the browser, and your page only has to send the file and write one tag. The Rails gem is one convenient way to do that, not a requirement — it needs Ruby >= 3.2 and Rails >= 8.0, and only if you choose it.
Installation — choose one
You need only one. Find the row whose condition matches your app, then read only that option’s section.
| Option | Use it when | What you do |
|---|---|---|
| gem | your app is Rails | add one line to your Gemfile, then make one helper call in a view. The helper writes the `` tag for you, so you never write that tag yourself |
| npm | your app already builds JavaScript — Vite, webpack, esbuild, Next.js… | install the package, import it once at your entry point, and write the `` tag yourself |
| CDN | neither of the above applies — Python, Go, PHP, plain HTML… | add one tag and write the tag yourself. No install, no build step |
All three load the same file and run the same widget. The first two pin the version for you — Bundler for the gem, your lockfile for npm — which is why they come first here. The CDN pins only a range written into a URL, so the last row
安装
This server does not publish a one-line install command.
Open the repository installation guide 新手？先看 mcpskill.org 教程 →