Enables the creation of Canvas Common Cartridge (.imscc) packages, allowing for the structured assembly of courses, modules, assignments, pages, and rubrics compatible with the Canvas Learning Management System.
Utilizes Instructure's canvas_cc framework to build standardized educational content cartridges that adhere to Canvas-profile Common Cartridge specifications.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@imscc-mcp Create a Canvas cartridge for 'English 101' including a rubric and two assignments."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Repo: https://github.com/InquiryInstitute/imscc_mcp
MCP server that builds Canvas Common Cartridge (.imscc) packages using Instructure’s Ruby gem canvas_cc. Cartridges are Canvas-profile CC files; many LMSes (including Populi) can import valid Common Cartridge 1.x zip/imscc.
Wiki/lesson pages from canvas_cc are type="webcontent" in imsmanifest.xml. Populi often skips them (you may see two errors for two pages). Assignments typically use associatedcontent/imscc_xmlv1p1/learning-application-resource and import more reliably. When authoring from imscc_template, run assemble-spec.mjs --populi to omit wiki pages and wiki module items; see docs/POPULI.md there.
Node.js ≥ 18
Ruby + Bundler
From this repo root: bundle install (installs gems into vendor/bundle per .bundle/config)
Related MCP server: canvas-mcp
cd ~/GitHub/imscc_mcp
bundle install
npm install
npm run buildbundle install
npm install
npm testRuns integration checks on ruby/build_cartridge.rb: successful builds produce a ZIP with imsmanifest.xml; invalid specs are rejected.
node dist/index.jsPoint command at node and args at the absolute path to dist/index.js after npm run build. No env vars are required.
Tool | Purpose |
| Build |
| Minimal JSON example for |
| Check |
| Links to |
output_directory: absolute path; created if missing.
course.title: required.
Assignments — Supported: groups, points, submission_types (e.g. online_text_entry, online_upload), due dates, HTML body. Link a rubric with rubric_identifier (must match a rubrics[].identifier), plus optional rubric_use_for_grading / rubric_hide_score_total.
Rubrics — rubrics[] with identifier, external_identifier (defaults to identifier), title, optional points_possible, and criteria[] each with id, description, points, and ratings[] (id, description, points, criterion_id matching the criterion id).
Slides / decks — There is no separate “slides” type. Package files (e.g. .pptx, .pdf) under files[] with identifier, file_path (path inside the course files tree), and file_location (absolute path on the machine that runs the build). Optionally add a module item with content_type Attachment and identifierref set to the file’s identifier (see canvas_cc module item types).
Module items — e.g. WikiPage + identifierref matching a page identifier, or ExternalUrl + url.
Assignments → groups — assignment_group_identifier_ref must match an assignment group identifier.
Importer support (Canvas vs Populi vs others) varies; test imports on your LMS.
For types not yet mapped in ruby/build_cartridge.rb (quizzes, question banks, full LTI, etc.), extend the script using the canvas_cc README.
MIT
Build a Canvas Common Cartridge (.imscc) using the Ruby canvas_cc gem. Requires Ruby+Bundler and bundle install in the imscc-mcp repo. Output is a Canvas-flavored CC file (often importable into Canvas, Populi, etc.).
Inputs: course (required), output_directory (required), files, pages, +6 more.
Pointers to upstream canvas_cc documentation and the IMS CC / Canvas relationship.
Inputs: no named parameters.
Verify Ruby, Bundler, and canvas_cc are available (bundle exec) from the imscc-mcp installation directory.
Inputs: no named parameters.
Returns a minimal JSON example you can adapt for imscc_build_cartridge.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct purpose: building the cartridge, providing documentation, checking environment prerequisites, and supplying an example spec. No overlap exists.
All tools share the 'imscc_' prefix, but the naming pattern is not fully consistent: 'build_cartridge' and 'check_environment' are verb_noun, while 'canvas_cc_reference' and 'example_spec' are noun phrases. However, the names are still readable and clearly indicate tool function.
With 4 tools, the server is well-scoped for its purpose of building IMSCC files. Each tool serves a necessary step in the workflow, and there is no bloat or shortage.
The toolset covers the core workflow: environment check, reference, example, and build. Minor gaps exist, such as a tool to validate or inspect a built cartridge, but the surface is adequate for the stated purpose.
The Canva MCP server connects AI assistants (like Claude, ChatGPT, and Cursor) to Canva's API, enabling them to create and manage designs directly within chat conversations. Key capabilities include generating new designs from prompts, autofilling templates, searching and resizing existing designs, importing files from URLs, exporting designs as PDFs or images, and managing folders and comments without switching between tools.
MCP server for the Inistate platform: module discovery, entry management, and activity submission.
A MCP server built for developers enabling Git based project management with project and personal…
Screenshots, PDFs, image editing, QR codes, email validation and more through one hosted MCP server.
