
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 分