Canvas MCP Server

Created By
enkhbold470a year ago
Overview

What is Canvas MCP Server?

Canvas MCP Server is a Model Context Protocol (MCP) server implementation designed to interact programmatically with the Canvas Learning Management System (LMS) API.

How to use Canvas MCP Server?

To use the Canvas MCP Server, clone the repository, install the dependencies, set up the required environment variables, build the project, and start the server. You can also integrate it with Cursor for enhanced functionality.

Key features of Canvas MCP Server?

  • Lists courses from Canvas LMS with optional enrollment type filtering.
  • Provides interactive help prompts for using the tools.

Use cases of Canvas MCP Server?

  1. Automating course management tasks in Canvas LMS.
  2. Integrating Canvas LMS functionalities into other applications.
  3. Enhancing user experience with interactive help prompts.

FAQ from Canvas MCP Server?

  • What are the prerequisites for using Canvas MCP Server?

You need Node.js 18 or later, a Canvas LMS instance, a Canvas API access token, and Cursor for client integration.

  • How do I connect Canvas MCP Server with Cursor?

You need to configure the MCP settings in Cursor to include the Canvas MCP Server details.

  • What should I do if I encounter issues?

Check your environment variables, verify your Canvas API token permissions, and consult the server logs for error messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
enkhbold470
Star
0
Language
TypeScript
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