orbits-mcp
Related Servers
Alternatives to orbits-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to search and describe API routes, retrieve people, admissions, academics, and billing records, download exports, and optionally make changes against a school information system, read-only by default.6161 npmMIT

Erstan Agent Tools Betaofficial
AlicenseNot gradedqualityCmaintenanceEnables building, optimizing, reviewing, and running AI agents and skills, plus managing authorized work items, in Erstan's QA environment via OAuth-authenticated MCP.Apache 2.0
Ridian MCP Serviceofficial
AlicenseNot gradedqualityCmaintenanceEnables authorized users to manage calendars, availability, tasks, contacts, sync operations, and Agent Mailbox email tools through an OAuth-scoped MCP connection.MIT- AlicenseAqualityBmaintenanceEnables AI coding agents to read TeamStorm tasks, comments, attachments, and links, and to perform limited write operations such as adding comments and updating task names, descriptions, or statuses through MCP.153MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access Canvas LMS academic data such as courses, assignments, grades, and events via MCP tools.-
- AlicenseNot gradedqualityAmaintenanceEnables students, instructors, and account administrators to interact with Canvas LMS APIs for managing courses, assignments, submissions, grades, enrollments, users, accounts, reports, discussions, modules, and files through MCP clients.21 npmMIT
TDQS
Scored across 39 tools
Most tools target a distinct resource+action: course, tag, user, test, question, and result operations are cleanly separated, and preview/execute and link/unlink pairs are explicitly distinguished in their descriptions. Minor overlap remains among the reporting tools (test_results, course_results, student_results, tag_summary, list_attempts) and between course_topics and course_access, where an agent could hesitate about which aggregate view to use.
Names are uniformly snake_case and mostly follow verb_noun (create_course, update_course, delete_tag, list_tests, get_test, find_users). The main deviation is the noun-first convention used for reporting/lookup tools (course_topics, course_access, test_results, tag_summary), which is internally fairly consistent but breaks the verb_noun pattern; create_users plural vs create_tag singular is a small inconsistency.
39 tools is heavy for an LMS admin surface and many are near-mechanical reversible pairs (link/unlink_tag_to_course, add/remove_students_from_tag, assign/remove_monitor_tag, grant/revoke_course_role) that could be consolidated into single tools with an action parameter. The breadth of the domain (users, tags, courses, tests, questions, results, edubits) justifies a large surface, but the count still exceeds a comfortable agent-facing set.
Coverage is broad: auth, user creation/update/password, tag lifecycle plus membership and monitor assignment, course CRUD with roles and access inspection, test import/export/append/publish, question update, and multiple result views plus edubit retroactive crediting. Remaining gaps are modest and partly API-imposed: no test deletion, no single-question creation or removal, and no user deletion, but agents can work around these via import/export and append operations.