camcors-mcp
Related Servers
Alternatives to camcors-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Canvas LMS enabling parent observers and students to access courses, assignments, grades, and more. Supports multiple authentication methods including token, OAuth, and a convenient fetchproxy fallback.19802 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS with automatic OAuth authentication. Enables interaction with courses, assignments, grades, modules, discussions, quizzes, files, calendar, messaging, and more without manual API token management.3,780 npmMIT
- FlicenseBqualityDmaintenanceA local MCP server that enables Codex to inspect and interact with Chrome tabs through the Chrome DevTools Protocol, primarily for collecting authorized Brightspace course materials into local folders.16-
- AlicenseAqualityAmaintenanceRead-only MCP server for Canvas LMS that works without API tokens by using session cookies, enabling AI assistants to access courses, assignments, grades, announcements, and more.3023 npm2MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for querying, validating, and analyzing student result data from a local database.-
- AlicenseNot gradedqualityDmaintenanceA local MCP server for Canvas LMS that enables querying courses, assignments, grades, modules, and more from any MCP-compatible AI client.11 npmMIT
TDQS
Scored across 14 tools
The tools have distinct purposes, with only a slight potential confusion between camcors_discard_report_preview (submission/deletion previews) and camcors_discard_preview (creation previews). Their descriptions clarify the difference, but the naming could be more distinct.
All tools follow a consistent verb_noun pattern with 'camcors_' prefix. Despite minor variation like 'discard_report_preview' vs 'discard_preview', the overall naming is predictable and logically structured.
With 14 tools, the server covers authentication, listing, reading, creation, editing, submission, and deletion workflows without being excessive. Each tool serves a clear step in the process, earning its place.
The tool set provides full lifecycle coverage for CamCORS reports: list, get, create, edit, submit, delete. The prepare/execute pattern ensures user confirmation steps are handled, leaving no obvious gaps in the standard workflow.