David Wicker

wicker-01

Products · 03/06

Wicker Study

A private study system for the exam ahead.

Course sources, planning, practice and Canvas updates in one workspace, with a tutor that answers only from your own material.

Sign-up is limited to university email addresses. Agents can use it too, through its MCP server.

Data
exam_study, 8.6 GB, files included
Accounts
Better Auth · university addresses only
Moved in
26 Oct 2026, from Neon by live replication
Open full screen ↵study.wicker.life ↗

study · Docker Compose · web, api and worker

webstudy.wicker.life

The Next.js app students work in.

Wicker Study, as it looks todayRecorded 28 Oct 2026 · this site can’t be embedded
apiMCP

Sign-in, the API, and an MCP server so agents can study alongside you.

workerqueue

Imports course material and runs long jobs from a Postgres queue.

Uses

postgres-mainpgvector · one database per appStalwartmail for every domainUmamivisits, no cookiesAI APIsOpenAI, Anthropic, Mistral

Beyond the server

  • Canvasthe university’s course platform
  • OpenAI, Anthropicthe tutor, with budgets per model

The story

01What it does

Wicker Study connects a student’s programme, results, timetable and Canvas courses to one private workspace: versioned course material, practice, assignment briefs, attendance, project progress, and a tutor that remembers context and answers from the student’s own sources.

The maintained library covers Statistics, Algorithmic Design, Embedded Programming, Computer Security and Numerical Methods. Connected Canvas courses extend it without mixing old retake material into current rules.

02Agents, with a hand on the brake

Local AI clients can use the same account over MCP. They can read freely, but every individual write needs the student’s explicit confirmation, and every request made with an API key shows up under Settings → AI activity.

03How it runs

Three services from one image: the web app, an API that also serves sign-in and the MCP server, and a worker that runs Canvas imports and long study jobs from a Postgres queue. Its database moved from Neon by live replication, so it never went offline during the move.