When should you use it?
- You teach on Canvas and repeat the same lookups weekly
- Answers need several API calls stitched together
- You can run a small local tool
Not for: Changing grades without review; Sharing identifiable student data with tools your institution has not approved
What do you need, and what do you get?
You need
- A Canvas API token
- Course IDs
- The questions you ask most often
You get
- A local tool the chat app can call
- Plain-English answers about submissions, grades and participation
How does it work, step by step?
- Check your institution's rulesConfirm you are allowed to use an API token and an AI assistant with course data.
- Start with one read-only questionHave the agent build a tool that only lists your courses, and test it.
- Add the lookups you repeatGrow to submissions, grade spreads and discussion activity, one tool at a time.
- Keep secrets out of codeStore the token in environment variables and run everything locally.
- Review before actingUse answers to decide whom to contact; make any grade changes yourself.
The prompt
Our own prompt, inspired by Vishal Sachdev and written to work in Claude Code and Claude. Values in lime are placeholders.
Build a small local MCP tool in Python that lets my assistant query Canvas with my API token from an environment variable. Start read-only with: list my courses; list assignments for a course; list students who have not submitted a given assignment. Handle pagination. Do not include any write actions. Add a README explaining setup and how to test each tool against the Canvas web interface.
Inspired by Vishal Sachdev: When Claude Code Becomes Your Co-Developer: Building a Canvas LMS Tool That Actually Works. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Canvas questions often need many paginated calls; test answers against the LMS by hand at first.
- Student privacy obligations still apply when the data passes through an assistant.
Our take
Vishal Sachdev's project is a model of how a non-developer can build the exact internal tool their job needs. He began with a single read-only question, which courses he teaches, and added lookups as real needs came up, so every feature earned its place. Keeping access tokens in environment variables rather than in the code is a habit every educator experimenting with AI should copy, especially before sharing scripts with colleagues. The main question to settle first is data protection. Student submissions, grades and analytics are covered by privacy rules such as FERPA in the US, and many institutions restrict which AI services may process them. Check your institution's policy before connecting, and prefer setups where student data stays on your machine or in an approved service. Keep grading decisions with you: an assistant can apply a rubric consistently and draft comments, but a grade affects a student, so review each one before it is saved. Write down which actions the tool can take, and keep anything that posts or changes grades behind a confirmation.
Where the time goes back: A question that took several screens of clicking becomes one sentence and one answer.
FAQ
Do I need to code?
Why a tool rather than an app?
Source and credit
Inspired by Vishal Sachdev. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- When Claude Code Becomes Your Co-Developer: Building a Canvas LMS Tool That Actually Works
- Creator
- Vishal Sachdev
- Published on
- chatwithgpt.substack.com (Substack)
- Original date
- Jun 20, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.