csa-skilljar
OfficialRelated Servers
Alternatives to csa-skilljar
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables managing Onde Inference accounts and model catalog operations through MCP tools such as login, app management, model registration, and assignment. Returns structured JSON over stdio for use with any MCP client.Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.18414 npmMIT
- FlicenseBqualityBmaintenanceEnables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.15-
- AlicenseNot gradedqualityCmaintenanceMCP server for Salesforce that exposes CLI, REST, Connect, Data 360, Bulk 2.0, and Einstein Models APIs as tools for any MCP-compatible client to manage orgs, data, and metadata.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables authors to drive the Leanpub author API from an MCP client: creating books, bundles, courses and tracks, previewing and publishing them, tracking job status, and pulling royalties, coupons, and reader email data. Runs locally over stdio with a Pro-plan API key resolved on each call, working around Leanpub's own hosted endpoint still returning 404s.MIT
- FlicenseAqualityBmaintenanceExposes the Polaris architectural fitness-function control plane's REST API as grouped MCP tools over stdio, letting agents manage tribes, squads, fitness targets and functions, measurement sources, submissions, evaluations, waivers, insights, and events. Handles Google OIDC login and silent token refresh automatically, and submits measurements with an ingest API key.16-
TDQS
Scored across 112 tools
Several tool pairs are genuinely confusable: delete_published_course performs identically to unpublish_published_course (its own description admits this), create_oauth_client and register_oauth_client both mint credentials with a load-bearing difference, and the v1/v2 progress tools (list_enrollments vs list_learner_progress) overlap. The descriptions work hard to disambiguate, but with 112 tools the misselection risk remains high.
The core list_/get_/create_/update_/delete_ convention is strong and mostly predictable, with batch writes consistently plural and single-object deletes singular. Minor deviations exist but are documented: delete_published_course is deliberately misleading, get_signup_field_value takes a non-standard parameter name, and meta tools like demonstration_plan break the verb_noun pattern.
112 tools is an extreme surface for any agent to navigate, even accounting for two API generations. The set includes deliberate duplicates (unpublish/delete published course, create/register OAuth client) and many read-only near-twins (list_labels/list_tags/list_course_labels) that could have been consolidated or split into separate servers by domain.
Core content lifecycle is well covered: courses, lessons, quizzes, question banks, groups, enrollments and published courses all have meaningful CRUD. But there are notable dead ends: no delete for courses or lessons, no webhook creation/update, and large v1 areas (promo codes, offers, ILT, paths) are read-only. Most gaps are documented as upstream API limits, but they will still cause agent failures when a user expects the full lifecycle.