ClassQuill MCP server

Give any MCP-aware AI tool — Claude, Codex, Cursor, Windsurf, Composio, and more —

read access to your ClassQuill tutoring-business data: sessions, students, tutors,

parents, invoices, payments, lesson plans, bookings, earnings, and reports.

It's a thin, read-only proxy over the ClassQuill public API

(`/v1`). Each tool maps 1:1 to a public API endpoint, so the tool list can never drift from

the real API. Your credentials never leave your machine (or, in hosted mode, your request).

> ClassQuill is the tutoring-business-management platform by EquateIt. The npm package is

> published as `equateit-mcp`.

Two ways to use it

1. Hosted (recommended — nothing to install)

Point any remote-MCP client at the hosted server:

https://mcp.classquill.com/mcp

• Claude / Claude.ai — add it as a custom connector and sign in (OAuth).
• Codex — `codex mcp add classquill --url https://mcp.classquill.com/mcp`
• Any client — pass your API key as a Bearer token: `Authorization: Bearer ei_live_…`

2. Local (run it yourself via npx)

npx -y equateit-mcp        # stdio, reads EQUATEIT_API_KEY

Claude Code:

claude mcp add classquill -e EQUATEIT_API_KEY=ei_live_xxxx -- npx -y equateit-mcp

Cursor / Claude Desktop / Windsurf (`mcpServers` config):

{
  "mcpServers": {
    "classquill": {
      "command": "npx",
      "args": ["-y", "equateit-mcp"],
      "env": { "EQUATEIT_API_KEY": "ei_live_xxxx" }
    }
  }
}

Getting an API key

Create one in the ClassQuill app under Settings → Developers (org admins). Keys look like

`ei_live_…` and are read-only for this server.

Tools

One read-only tool per `/v1` GET route — sessions, students, tutors, parents, invoices,

payments, lesson-plans, homework, questions, subjects, files, results, availabilities,

coverage, reports, and more. The list is generated from the public OpenAPI spec

(`npm run gen:tools`) so it always matches the live API.

Options & environment

In HTTP mode, each request supplies its own credential as `Authorization: Bearer …` — an

`ei_live_…` API key or an OAuth access token.

Develop

npm install
npm run build     # → dist/
npm test          # unit tests (url builder + auth scheme)

Self-hosting the HTTP server is a single container — see `Dockerfile`.

License

MIT — see `LICENSE`.