pi-roundtable 0.5.0 → 0.5.2

package/CHANGELOG.md

@@ -5,6 +5,18 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.5.2] - 2026-10-02
+
+### Changed
+
+- `pi-mcp-adapter` is 5.0.0 (was 4.0.0). The core supplies its servers through `createMcpAdapter()`, which 5.0.0 keeps isolated: it reads no `mcp.json` and leaves the host's Pi settings alone. Checked on pi 0.99.2 and 1.0.0 by connecting a session built the way the core builds one to a local MCP server that requires a bearer token: the tool registered, a call returned its result, and the agent directory got no `settings.json`. 5.0.0 declares pi-ai peer support up to 0.99; the checks above ran it on 1.0.0.
+
+## [0.5.1] - 2026-10-02
+
+### Changed
+
+- `@earendil-works/pi-ai` and `@earendil-works/pi-coding-agent` take `>=0.99.2 <2`, so hosts can run pi 1.0. The typecheck, lint and full test suite pass on pi 1.0.0, and a session built the way the core builds one still connects `pi-mcp-adapter` 4.0.0 to a bearer-protected MCP server and calls its tool. The lockfile stays on 0.99.2, the lowest tested version, and the daily canary now runs the newest 1.x.
+
 ## [0.5.0] - 2026-10-01
 
 ### Changed

package/README.md

@@ -2,17 +2,25 @@
 
 English | [Traditional Chinese](README.zh-TW.md)
 
-A Discord agent server on [Pi](https://github.com/earendil-works/pi).
-You get a team of AI agents in one Discord server: each agent owns a channel and a conversation, they share tools and memory, and you extend the bot with plugins written in TypeScript.
+Docs: <https://pi-roundtable.wayneh.tw>
+Source and issues: <https://github.com/wayne930242/pi-roundtable>
 
-- Built for one owner and one Discord server. Others can be allowed to talk to the agents, but that setup, and its risks, are the operator's.
-- Bun only. The package ships its TypeScript source, so there is no build step.
+A Discord agent server on [Pi](https://github.com/earendil-works/pi).
+Each AI agent has its own channel and conversation in your Discord server.
+They share tools and memory.
+You can extend the bot with TypeScript plugins.
+
+- Built for one owner and one Discord server.
+  You can allow others to talk to the agents, but that setup and its risks are the operator's.
+- Bun only.
+  The package ships its TypeScript source, so there is no build step.
 - MIT licensed.
 
 ## What you need
 
 - [Bun](https://bun.sh/docs/installation) 1.3 or newer.
-- PostgreSQL. The project `init` creates has a `docker-compose.yml` that runs one.
+- PostgreSQL.
+  The project `init` creates has a `docker-compose.yml` that runs one.
 - A Discord bot: an application with a bot user, the Message Content intent turned on, and an invitation to your server.
 - A model login: the API key of the provider of the model you choose (`ANTHROPIC_API_KEY` for `anthropic/...`), or a login made with Pi.
 - An address that reaches the process from the internet, such as a tunnel, because Discord fetches the agents' avatars from it.
@@ -29,7 +37,7 @@ bunx roundtable doctor
 bunx roundtable start
 ```
 
-`init` writes a working project and asks for no secret.
+`init` writes a working project without asking for secrets.
 It refuses to write anything when Bun is missing or too old, or when a file it would create already exists.
 
 ### `.env`
@@ -54,7 +62,8 @@ Bun loads `.env` by itself, and `.gitignore` keeps it out of Git.
 2. `.env` has a value for every variable `.env.example` lists.
 3. `roundtable.config.ts` against its schema, naming the failing key.
 4. Every plugin loads, and no two share a name.
-5. Whether a plugin fills the `images` slot. Without one is not a failure: agents get avatars generated from their display names.
+5. Whether a plugin fills the `images` slot.
+   The check passes with or without one; agents without an image provider get avatars generated from their display names.
 6. PostgreSQL is reachable and migratable.
 7. The Discord token is valid, the bot is in your server, the Message Content intent is on, and the bot has the permissions it needs in the entry channel (including Pin Messages).
    When the bot is not in the server, the fix is an invitation link that asks for exactly those permissions.
@@ -67,7 +76,7 @@ A fresh project fails only on the credentials you have not entered yet, and says
 ### `start`
 
 `bunx roundtable start` runs the checks that need no network, stops with the same message `doctor` prints when one fails, and otherwise starts the bot.
-Once it runs, the agents in `agents.ts` have their channels, and `/roundtable schedule list` shows their schedules.
+The running bot gives the agents in `agents.ts` their channels, and `/roundtable schedule list` shows their schedules.
 On `SIGTERM` or `SIGINT` it finishes running work before it stops.
 
 ## A plugin
@@ -95,7 +104,7 @@ export const hello = definePlugin({
 });
 ```
 
-It is tested without Discord or PostgreSQL:
+You can test it without Discord or PostgreSQL:
 
 ```ts
 import { expect, test } from "bun:test";
@@ -111,14 +120,33 @@ test("hello greets", async () => {
 
 The [plugin guide](docs/plugins.md) explains every part a plugin can add (tools, prompt sections, agents, events, services, migrations, providers, slash commands, HTTP routes, and more), the order things start and stop in, and every startup error with its fix.
 Its examples live in [`examples/`](examples), and the test suite runs each of them.
-`pi-roundtable/kit` supplies claim, tool and presentation helpers and type-only names for the context’s existing services, and `pi-roundtable/discord` supplies the slash-command registrar, owner-command and panel helpers, and the agent panel, and is the entry that names discord.js types (`pi-roundtable/testing` names a few, through `testHost`'s composed commands); both are versioned like the main entry: before 1.0 a breaking change comes in a minor release and is listed in the changelog.
+`pi-roundtable/kit` supplies claim, tool and presentation helpers and type-only names for the context’s existing services.
+`pi-roundtable/discord` supplies the slash-command registrar, owner-command and panel helpers, and the agent panel.
+It is the entry that names discord.js types (`pi-roundtable/testing` names a few, through `testHost`'s composed commands).
+Both follow the main entry's versioning: before 1.0, breaking changes come in minor releases and are listed in the changelog.
+
+## MCP connectors
+
+The separate package [pi-roundtable-mcp](https://www.npmjs.com/package/pi-roundtable-mcp) connects the bot to the MCP ecosystem in both directions, with two plugins:
+
+- `mcpConnectors`: you add an MCP server in Discord with a private form, such as Notion, a calendar, or anything that speaks MCP over HTTP.
+  Your code then gives its tools to the agents you choose.
+  A [ContextForge](https://github.com/IBM/mcp-context-forge) gateway that you run keeps each server and its token.
+- `remoteMcp`: an agent outside Discord sends your agent a message over MCP and reads the answer.
+  It can also use the Discord channels you grant, with only the operations you choose.
+
+```sh
+bun add pi-roundtable-mcp
+```
+
+It works with pi-roundtable 0.4 and 0.5, and its README lists every option.
 
 ## Settings
 
 `roundtable.config.ts` holds the settings and the list of plugins.
 An unknown key is an error that names the closest known one.
 
-The language of what the bot shows in Discord is the `locale` setting: `en` by default, or `zh-TW`.
+`locale` sets the language of the bot's Discord text: `en` by default, or `zh-TW`.
 
 ```ts
 export default {

package/README.zh-TW.md

@@ -2,10 +2,13 @@
 
 [English](./README.md) | 繁體中文
 
+文件：<https://pi-roundtable.wayneh.tw>
+原始碼與 issue：<https://github.com/wayne930242/pi-roundtable>
+
 一個建立在 [Pi](https://github.com/earendil-works/pi) 上的 Discord 智慧體（agent）伺服器。
-你會在一個 Discord 伺服器裡得到一組 AI 智慧體：每個智慧體擁有一個頻道和一段對話，彼此共用工具與記憶，你用 TypeScript 寫外掛（plugin）來擴充這個 bot。
+它在你的 Discord 伺服器裡放一組 AI 智慧體：每個有自己的頻道和對話，共用工具與記憶。想加功能，就用 TypeScript 寫外掛（plugin）。
 
-- 為一位擁有者和一個 Discord 伺服器設計。你可以允許其他人與智慧體對話，但這樣的設定與風險由營運者自行承擔。
+- 為一位擁有者和一個 Discord 伺服器設計。其他人也能跟智慧體對話，風險由營運者自行承擔。
 - 只支援 Bun。套件直接發佈 TypeScript 原始碼，不需要建置步驟。
 - MIT 授權。
 
@@ -13,9 +16,9 @@
 
 - [Bun](https://bun.sh/docs/installation) 1.3 以上。
 - PostgreSQL。`init` 建立的專案附有 `docker-compose.yml`，可以直接啟動一個。
-- 一個 Discord bot：一個含 bot 使用者、已開啟 Message Content intent，並已邀請進你的伺服器的應用程式。
-- 模型登入：你選的模型的供應商 API key（`anthropic/...` 用 `ANTHROPIC_API_KEY`），或用 Pi 做過的登入。
-- 一個能從網際網路連到這個行程的位址，例如通道（tunnel），因為 Discord 會從該位址取得智慧體的頭像。
+- 一個 Discord bot：有 bot 使用者、開了 Message Content intent，也已經邀請進你的伺服器。
+- 模型登入：你選的模型的供應商 API key（`anthropic/...` 用 `ANTHROPIC_API_KEY`），或之前用 Pi 登入過的帳號。
+- 一個從網際網路連得到這個行程的位址，例如通道（tunnel）。Discord 要從這個位址抓智慧體的頭像。
 
 ## 五分鐘上手
 
@@ -29,13 +32,13 @@ bunx roundtable doctor
 bunx roundtable start
 ```
 
-`init` 會寫出一個可運作的專案，不會向你要任何祕密資訊。
-Bun 不存在或版本太舊，或它要建立的檔案已經存在時，它不會寫入任何東西。
+`init` 會寫出一個能跑的專案，過程不會問你任何祕密資訊。
+Bun 沒裝、版本太舊，或要建立的檔案已經存在時，它什麼都不寫。
 
 ### `.env`
 
 `.env.example` 說明了每個值的來源。
-Bun 會自行載入 `.env`，`.gitignore` 也已讓它不進 Git。
+Bun 會自己讀 `.env`，`.gitignore` 也已經擋掉它。
 
 | 變數 | 內容 |
 | --- | --- |
@@ -54,15 +57,15 @@ Bun 會自行載入 `.env`，`.gitignore` 也已讓它不進 Git。
 2. `.env` 對 `.env.example` 列出的每個變數都有值。
 3. `roundtable.config.ts` 符合其 schema，失敗時指出是哪個鍵。
 4. 每個外掛都能載入，且沒有兩個外掛同名。
-5. 是否有外掛填入 `images` 槽位。沒有並不算失敗：智慧體會用顯示名稱產生頭像。
+5. 有沒有外掛填了 `images` 槽位。沒有也不算失敗，智慧體會用顯示名稱產生頭像。
 6. PostgreSQL 連得上，且能執行 migration。
 7. Discord token 有效、bot 已在你的伺服器裡、Message Content intent 已開啟，而且 bot 在入口頻道有它需要的權限（包含 Pin Messages）。
-   bot 不在伺服器裡時，修正方式是一個邀請連結，連結要求的正是這些權限。
+   bot 還不在伺服器裡的話，它會給你一個邀請連結，連結已經帶好這些權限。
 8. 模型登入存在。
-9. `PUBLIC_URL` 是格式正確的位址；加上 `--reachable` 時它還必須有回應，這只有在 bot 執行中才成立。
+9. `PUBLIC_URL` 的格式正確；加上 `--reachable` 還要求它有回應，所以 bot 得先跑起來。
 
-任何一項失敗，它就以非零狀態結束，並且不更動它檢查過的任何東西。
-全新的專案只會因為你還沒填的憑證而失敗，而且會指出是哪些。
+只要有一項失敗，就以非零狀態結束，檢查過程不會改動任何東西。
+全新的專案只會卡在還沒填的憑證，它會列出是哪幾個。
 
 ### `start`
 
@@ -111,7 +114,25 @@ test("hello greets", async () => {
 
 [外掛指南](docs/plugins.md)（英文）說明外掛能新增的每個部分（工具、提示詞區段、智慧體、事件、服務、migration、provider、斜線指令、HTTP 路由等等）、啟動與停止的順序，以及每一種啟動錯誤和它的修正方式。
 指南裡的範例放在 [`examples/`](examples)，測試套件會執行每一個範例。
-`pi-roundtable/kit` 提供頻道認領（claim）、工具與呈現用的輔助函式，以及 context 現有服務的純型別名稱；`pi-roundtable/discord` 提供斜線指令註冊器、擁有者指令與面板的輔助函式，以及智慧體面板，是會用到 discord.js 型別的入口（`pi-roundtable/testing` 也透過 `testHost` 組合出的指令用到少數幾個）。這兩個入口的版本規則與主入口相同：1.0 之前，不相容的變更會放在次版本（minor）發佈，並列在變更記錄中。
+`pi-roundtable/kit` 提供頻道認領（claim）、工具與呈現用的輔助函式，以及 context 現有服務的純型別名稱。
+`pi-roundtable/discord` 提供斜線指令註冊器、擁有者指令與面板的輔助函式，以及智慧體面板；它是會用到 discord.js 型別的入口（`pi-roundtable/testing` 也透過 `testHost` 組合出的指令用到少數幾個）。
+這兩個入口的版本規則與主入口相同：1.0 之前，不相容的變更會放在次版本（minor）發佈，並列在變更記錄中。
+
+## MCP connector
+
+獨立套件 [pi-roundtable-mcp](https://www.npmjs.com/package/pi-roundtable-mcp) 用兩個外掛，把 bot 雙向接上 MCP：
+
+- `mcpConnectors`：你在 Discord 用私人表單加入一台 MCP server，例如 Notion、行事曆，或任何用 HTTP 提供 MCP 的服務。
+  接著由你的程式碼把它的工具交給你選的智慧體。
+  每台 server 和它的 token 由你自己架的 [ContextForge](https://github.com/IBM/mcp-context-forge) gateway 保管。
+- `remoteMcp`：Discord 以外的智慧體透過 MCP 傳訊息給你的智慧體，並讀取回答。
+  它也能使用你授權的 Discord 頻道，而且只限你選的操作。
+
+```sh
+bun add pi-roundtable-mcp
+```
+
+它支援 pi-roundtable 0.4 和 0.5，每個選項都列在它的 README。
 
 ## 設定