courseforge-mcp

CourseForge turns a syllabus into a real Canvas course. Hand your AI assistant a course outline and get back modules, pages, assignments, quizzes with questions, and discussions, imported straight into Canvas LMS or packaged as a standards-compliant .imscc file that any Canvas instance can import.

Why CourseForge?

Existing Canvas MCP servers read courses well, and some create individual pages or assignments. CourseForge builds the whole course: it generates a Canvas-flavored IMS Common Cartridge (the same format Canvas itself exports) and pushes it through Canvas's content-migrations API, so one import call creates every module, page, assignment, and quiz. The content arrives unpublished, and you review it in Canvas before students see anything.

Related MCP server: imscc-mcp

Quickstart

1 · MCP server: let your AI build courses in Canvas

npx -y courseforge-mcp init        # interactive: writes config for Claude Code/Desktop/Cursor

Then ask your assistant: “Here's my syllabus. Build it into Canvas course 12345.”

claude mcp add courseforge \
  -e CANVAS_BASE_URL=https://youruni.instructure.com \
  -e CANVAS_API_TOKEN=your-token \
  -- npx -y courseforge-mcp

Get a token in Canvas: Account → Settings → + New access token.

2 · No API token? Build an importable file instead

npx -y @courseforge/imscc build examples/intro-to-chemistry.json

Upload the resulting .imscc in Canvas under Settings → Import Course Content → Common Cartridge 1.x Package.

3 · Agent skills for Claude Code, Codex, Cursor & 40+ agents

npx skills add jasp-nerd/courseforge      # canvas-course-builder, imscc-editor, canvas-course-qc

What you get

How it works

flowchart LR
    A["📄 Syllabus / course idea"] --> B["🤖 AI agent<br/>+ canvas-course-builder skill"]
    B --> C["CourseSpec JSON<br/>Zod-validated"]
    C -->|"@courseforge/imscc"| D["📦 .imscc<br/>Canvas cartridge"]
    D -->|"content_migrations API"| E["🎓 Canvas course<br/>unpublished, ready for review"]
    D -->|"manual upload"| E
    C -->|"mode: api"| E
    E -->|"export"| D

A plain JSON course description called the CourseSpec connects everything. Agents write it, the imscc package turns it into a cartridge with the same structure Canvas's own exports use (including the canvas_export.txt flag and cccv1p0 extension XMLs, which preserve module structure and assignment settings on import), and the MCP server pushes it through the same import pipeline as the Canvas UI.

Compared to existing Canvas MCP servers

vishalsachdev's and bruchris's servers cover course management (grading, feedback, student workflows) far more deeply than CourseForge does. CourseForge covers creation. They run side by side without conflict.

Repository layout

packages/shared          CourseSpec Zod schemas (the shared course format)
packages/imscc           .imscc build / parse / modify / validate + CLI
packages/canvas-client   Canvas REST client (zero MCP dependencies)
packages/mcp             The courseforge-mcp server
skills/                  Agent Skills (open SKILL.md standard)
fixtures/                Real .imscc exports used in round-trip tests
docs/                    IMSCC format ground truth, specs, launch playbook

Documentation

• The Canvas .imscc format — ground truth

• CourseSpec reference

• Contributing · Code of Conduct

Roadmap

• Chrome extension (build courses from inside the Canvas UI, no token needed)

• Rubrics + outcomes in cartridges

• New Quizzes (QTI 2.x) authoring

• Course templates gallery

• .mcpb one-click bundle on the MCP registries

License

Apache-2.0 © jasp-nerd. Not affiliated with Instructure. Canvas is a trademark of Instructure, Inc.