School MCP

Created By
54yyyua year ago
A Model Context Protocol (MCP) server for academic tools, integrating with Canvas and Gradescope platforms.
Overview

what is School MCP?

School MCP is a Model Context Protocol (MCP) server designed for academic tools, facilitating integration with platforms like Canvas and Gradescope.

how to use School MCP?

To use School MCP, clone the repository, install the package, and set up your environment variables. You can run the server directly or use a convenience script.

key features of School MCP?

  • Fetch and display upcoming assignment deadlines from Canvas and Gradescope.
  • Integrate deadlines with macOS Calendar or Reminders using AppleScript.
  • Download course materials from Canvas.

use cases of School MCP?

  1. Managing assignment deadlines for students.
  2. Syncing academic schedules with personal calendars.
  3. Downloading course materials for offline access.

FAQ from School MCP?

  • Can School MCP integrate with other platforms?

Currently, it is designed to work with Canvas and Gradescope.

  • Is there a setup helper?

Yes! A setup helper is included to configure the server automatically.

  • What programming language is School MCP written in?

School MCP is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
54yyyu
Star
3
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago