convez.ai
MCP ServerAutomaçãoIntermediário
Ryfter

Canvas Toolchain

Ryfter/canvas-toolchain

Ferramenta integrada para atualizar cursos Canvas com IA

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que automatiza o redesenho de cursos no Canvas LMS a cada semestre. Combina análise curricular, geração de HTML seguro para Canvas e orquestração de publicação através de uma interface única, com instalador nativo e arquitetura modular.

Instalação

$npx convez-ai Ryfter/canvas-toolchain

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
57%
Último commit
há 6 dias
Versão
v2.4.2
Issues abertas
11
Contribuidores
1

Casos de uso

  • Atualizar conteúdo de cursos Canvas automaticamente a cada semestre
  • Analisar cursos anteriores e planejar melhorias curriculares
  • Gerar HTML seguro para Canvas sem risco de incompatibilidade
  • Integrar módulos adicionais como vídeos de palestras

Veredito

Solução robusta e bem estruturada para educadores que usam Canvas LMS. O design modular, documentação completa e instalador nativo reduzem fricção de adoção, mas é direcionado a um nicho específico (Canvas LMS). Excelente para professores que precisam automatizar ciclos de redesenho curricular.

README

A tradução para o português deste README ainda está na fila.

canvas-toolchain

A toolchain that helps a professor refresh a Canvas LMS course every semester. It combines three apps — Curriculum Intelligence, Canvas Design Studio, and Command & Control — behind a single MCP entrypoint, plus a Python sidecar for downloading Canvas data and a native installer.

Canvas Backup archive
  -> Curriculum Intelligence   (analyze past course, plan the next one)
  -> Canvas Design Studio      (generate Canvas-safe HTML)
  -> Canvas-safe HTML
  -> optional Canvas publishing

Professors drive the whole thing by talking to the Command & Control MCP server from any MCP-capable AI client (Claude Desktop, Claude Code, ChatGPT, Gemini). Each underlying app also stays independently usable. Direct Canvas API publishing is always optional — the no-token "generate HTML and paste it in" path is first-class.

Where to start

  • Installing as a user? Download the native installer (Windows x64 / macOS arm64) from Releases — it bundles Node, the toolchain, and an auto-updater behind a five-screen wizard.
  • Working on this repo (human or AI agent)? Read AGENTS.md first — it maps the tools, skills, packages, and workflow conventions, and links to every per-package handoff doc.
  • Latest repo health review: docs/repo-health-check-2026-06-07.md.

Documentation

DocWhat's in it
🚀 User Guide & TutorialStart here. What you can do, how to use it, a hands-on end-to-end tutorial, and a task-by-task command catalog (what each command is · how it works · why you'd use it)
📘 Commands & Credentials referenceEvery command (MCP tool) with its parameters, and every API key/secret — what it's for, why, and whether it's optional
🧩 Module viewThe toolchain broken into modules: what each is, why it exists, what it does, and its commands
🎨 Visual guidePicture-first tour — diagrams of the pipeline, architecture, and setup (rendered PNG/SVG + an editable Excalidraw scene)

What lives where

PathWhat it owns
packages/command-and-control/Single professor-facing MCP entrypoint; workflow orchestration, registry, adapters
packages/canvas-design-studio/Canvas-safe HTML generation, design review, transcript enrichment
packages/curriculum-intelligence/Course analysis, semester comparison, topic currency, planning
packages/shared-types/TypeScript contracts shared across packages
packages/shared-llm/Shared LLM client (Anthropic + Ollama providers)
packages/module-contract/The CanvasToolchainModule plug-in contract for opt-in capability modules
packages/module-video/Lecture Video module (Panopto as the first provider)
installer/Go + Fyne native installer and auto-updater
canvas-backup (separate repo)Python Canvas backup downloader, reached via a CLI bridge

Verification

From the repo root:

npm test          # all TypeScript workspace tests
npm run build     # compile all packages
npm run smoke:integration --workspace=packages/command-and-control

Installer (from installer/):

go vet ./...
go test ./...
go build -o ct-installer.exe .

See AGENTS.md for the full cross-package verification matrix and the installer's local-payload build notes.

Ver o original no GitHub

Bom para

Relacionados