
Campus Copilot MCP
io.github.xiaojiou176-open由 GitHub 帳號 xiaojiou176-open 發布v0.1.1更新於 Oct 24, 2026
Read-only MCP server for the local Campus Copilot BFF and imported workspace snapshots.
概覽
一個本機唯讀 MCP 伺服器,讓助理查詢 Campus Copilot BFF 並檢視已匯入的校園工作區快照。
- 可以做什麼
- 檢查本機 Campus Copilot 後端的健康狀態與各提供者狀態,並透過提問工具向其發問。檢視來自 Canvas、Gradescope、EdStem 和 MyUW 的已匯入快照。匯出快照產物。全部為唯讀操作,依據本機快照或輕量本機 BFF,而非即時校園網站。
- 適用情境
- 當你已在本機執行 Campus Copilot,並想為 Codex 或 Claude Code 風格的本機工作流程提供最小的單一伺服器入口,用來讀取已匯入的課程與校園快照時使用。它不適用於即時網站控制、選課註冊自動化或上傳課程檔案。
- 執行需求
- 以 stdio 啟動的本機程序,透過 GitHub Release 託管的 .mcpb 套件散布;README 的安裝方式是在儲存庫中以 pnpm 建置。需要本機 Campus Copilot BFF 或已匯入的工作區快照可用。未宣告驗證、環境變數或標頭。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Campus Copilot MCP,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
@campus-copilot/mcp-server
Read-only MCP server for the local CampusCopilot BFF and imported workspace snapshots.
This is the generic MCP entry point used by the integration examples under examples/integrations/.
Use this package when you want the smallest single-server entry point for Codex / Claude Code-style local MCP workflows.
If you are still choosing between the generic MCP server, site sidecars, CLI, or SDK surfaces, start with ../../examples/toolbox-chooser.md first.
Install
Current install status: repo-local public surface with a bundled JS server artifact. The official MCP Registry lane now uses a GitHub release-hosted .mcpb bundle for this server; discovery-page read-back is still a separate proof step.
From the repo root:
Shared public-preview proof loop from the repo root:
First command to try:
Registry-unblock progress in this repo:
- the published bin now targets a bundled
dist/bin.mjsartifact instead of a raw TypeScript entrypoint - the registry path now ships a release-hosted
.mcpbbundle instead of relying on a public npm scope that does not exist - preregistry metadata now lives beside the package in
server.jsonand the package-levelmcpName - the bundle manifest now lives in
mcpb.manifest.json - repo-side submit-ready fields now also live in
registry-submission.packet.json - the public distribution router lives in
../../DISTRIBUTION.md - registry discovery-page read-back is still a separate upstream step; this README does not imply the listing UI has already been re-read
Registry preflight proof from the repo root:
That preflight checks the late-stage alignment work that tends to drift:
package.json#mcpNameserver.jsonrelease asset URL / SHA / transport alignmentmcpb.manifest.jsonversion and entry-point alignment- the monorepo
subfolderpath - example config plus truthful install wording
- the repo-owned submission packet that the owner can reuse later
Related public distribution doc:
Pair It With The Container Path
The current Docker surface is intentionally the thin local BFF, not this stdio server itself.
That split is on purpose:
- the stdio MCP server stays the local read-only MCP entrypoint
- the Docker path gives the repo one truthful HTTP and health-check surface
- together they keep the product local-first instead of pretending CampusCopilot is a hosted MCP service
Build the containerized BFF from the repo root:
Use the container path when you need a local HTTP surface or container-friendly healthcheck. Keep using this package when you need the local stdio MCP server. If you want the shortest rule in one sentence: pair it with the local stdio MCP server, and treat the Docker route as a local HTTP helper, not a hosted API.
You can also launch the local container directly without Compose:
Current tools
campus_healthproviders_statusask_campus-copilotcanvas_snapshot_viewgradescope_snapshot_viewedstem_snapshot_viewmyuw_snapshot_viewexport_snapshot_artifact
Boundary
- local-first
- read-only
- stdio
- snapshot-first or thin-BFF-first
- not a hosted MCP service
- not a hosted API
- not a live-browser control plane
- not a campus-site mutation surface
- not a registration-automation surface
- not a raw course-file AI upload surface
Use the same academic safety contract here as everywhere else:
See also
../../examples/toolbox-chooser.md../../examples/integrations/README.md../../examples/integrations/codex-mcp.example.json../../examples/integrations/codex-mcp-shell.example.json../../examples/integrations/claude-code-mcp.example.json../../examples/integrations/claude-code-mcp-shell.example.json../../examples/openclaw-readonly.md
來源:packages/mcp-server/README.md,提交 b28442e
工具
0版本歷史
1- v0.1.1最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分