convez.ai
MCP ServerIntegração & APIsIntermediário
04ipatel

AccessCanvas

04ipatel/AccessCanvas

Conexão limpa entre Claude e Canvas LMS para gerenciar cursos e tarefas

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que conecta Claude Desktop ao Canvas LMS, permitindo consultar cursos, tarefas, notas e arquivos diretamente na conversa. Funciona como uma camada de dados confiável que fornece informações atualizadas do Canvas sem cache, deixando a inteligência (reconciliação de prazos, organização de estudos) para Claude.

Instalação

$npx convez-ai 04ipatel/AccessCanvas

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Consultar prazos e tarefas vencidas da semana no Canvas
  • Baixar arquivos de disciplinas e assignments automaticamente
  • Verificar notas e acompanhar desempenho acadêmico
  • Integrar dados do Canvas em automações e assistentes Claude

Veredito

Ferramenta bem-arquitetada que respeita separação de responsabilidades: fornece acesso limpo ao Canvas e deixa a lógica inteligente para Claude. Útil para estudantes e educadores que já usam Canvas e querem automação em Claude, mas requer setup local (Node.js, tokens de API).

README

A tradução para o português deste README ainda está na fila.

By ishu

A tool that lets Claude (the AI) read your Canvas courses, assignments, grades, and files. Ask Claude things like "what's due this week?" or "download the files from Assignment 2" and it just works.

Reach out if you have questions or want new features.


The bigger picture (what this is really for)

Canvas alone isn't the full story of your classes — professors announce deadlines out loud, the real schedule often lives in a syllabus PDF, and some professors turn off Canvas features. So this tool doesn't try to be smart about your courses. It does one job well: it's the clean, reliable connection to Canvas. Think of it as a tap that gives Claude exactly the Canvas data it asks for — your courses, assignments, grades, files — fresh every time, nothing cached, no guessing.

The smart part happens in Claude, on top of this tool: keeping a running "brain" for each class (a trusted summary at the top, a running log of new things at the bottom), reconciling what a professor said in lecture against what's on Canvas, reading PDFs, and eventually helping you study on a schedule instead of cramming. That intelligence lives in your Claude automations — not in this tool. AccessCanvas just feeds it reliable Canvas data.

In short: this is the foundation — a boring, dependable data layer — that makes the clever, grade-helping stuff possible and trustworthy. Full design notes live in docs/reference/architecture.md.


What you need before starting

  • A Mac or Windows computer
  • Claude Desktop installed
  • A Babson Canvas account
  • About 10 minutes

Step 1 — Install Node.js

Node.js is the engine that runs this tool. You probably don't have it yet.

  1. Go to nodejs.org
  2. Click the big green "LTS" download button
  3. Open the downloaded file and follow the installer

To confirm it worked, open Terminal (Mac) or Command Prompt (Windows) and type:

node --version

You should see something like v20.11.0. Any number above 18 is fine.


Step 2 — Download AccessCanvas

In Terminal, run:

git clone https://github.com/04ipatel/AccessCanvas.git
cd AccessCanvas

If you get git: command not found, install Git from git-scm.com first.


Step 3 — Install dependencies

npm install

This downloads the packages AccessCanvas needs. Takes about 30 seconds.


Step 4 — Run the setup wizard

npm run setup

The wizard will walk you through everything:

Canvas URL — just press Enter to use the Babson default (https://babson.instructure.com).

API token — this is how Canvas knows it's you. To get one:

  1. Log in to Canvas
  2. Click your profile picture (top right) → Settings
  3. Scroll down to Approved Integrations
  4. Click + New Access Token
  5. Name it anything (e.g. "Claude") → click Generate Token
  6. Copy the token — you won't be able to see it again after closing that window

Paste it into the wizard. It will validate the token live and tell you if it worked.

Timezone — the wizard detects yours automatically. Just press Enter to confirm.

Download folder — where Canvas files will be saved on your computer. Press Enter to use the default (~/Academics).

Claude Desktop config — the wizard will ask if it should configure Claude Desktop automatically. Say yes. This is what connects Claude to AccessCanvas.


Step 5 — Build

npm run build

Compiles the code. Takes a few seconds.


Step 6 — Restart Claude Desktop

Fully quit Claude Desktop and reopen it. AccessCanvas will appear in Claude's tool list (look for the tools icon in the chat bar).


You're done

Try asking Claude:

  • "What assignments do I have coming up?"
  • "Show me my grades for QTM3310"
  • "Download the files from Assignment 2 in FIN4507"

Tools Claude can use

ToolWhat it does
list_coursesLists your active courses
get_assignmentsEvery assignment for a course — due dates, points, instructions, attached files
get_gradesYour overall grade in each course
get_assignment_gradesScores and submission status, assignment by assignment
get_announcementsRecent announcements for a course
get_modulesModule/week structure for a course
get_module_itemContent of a specific module page
list_filesFiles a course makes available
download_fileDownloads a file to your computer

Troubleshooting

Claude doesn't show AccessCanvas after restarting Make sure you ran npm run build before restarting. If still missing, check that the setup wizard successfully wrote the Claude Desktop config (it will confirm this at the end).

Token keeps getting rejected Make sure you copied the full token — they're long. Regenerate one in Canvas if needed.

npm install fails Your Node.js version might be too old. Re-download from nodejs.org and pick the LTS version.

Files are downloading to the wrong place Re-run npm run setup — it will let you change the download folder.


Development

npm test           # run tests
npm run test:watch # watch mode
npm run build      # compile TypeScript
Ver o original no GitHub

Bom para

Relacionados