Skip to main content

What is an MCP Server?

MCP is an open protocol that standardizes how applications provide context to LLMs. Among other benefits, it gives LLMs tools to act on your behalf. The EquateIt MCP server lets MCP-aware tools — Claude Code, Claude Desktop, Cursor, Windsurf and others — read your organisation’s tutoring data through the EquateIt public API. It is read-only and scoped to your org, exactly like the REST API.
Prefer not to install or run anything? Use the hosted server at https://mcp.classquill.com/mcp instead — see AI Connectors to connect Claude (via OAuth), Codex, Composio and others. This page covers running the equateit-mcp package yourself.
Also listed on the Smithery registry: smithery badge

What it can do

One tool per public endpoint, all read-only:
  • Sessions — list and fetch tutoring sessions
  • Tutors — list tutors and pull per-tutor earnings
  • Payments & invoices — list payments received and invoices issued
  • Students & parents — list students, parents, and a parent’s balance
  • Curriculum — subjects, classrooms, student groups, lesson plans, homework, results
  • Operations — mileage trips, expense claims, and an owner reports summary
As an example, you could ask “How much did each tutor earn last week?” or “List the invoices that are still outstanding.”

Prerequisites

  • Node.js 18 or later
  • An EquateIt API key — create one in Settings → Developers (org admins only). See Authentication.

How to use the MCP Server

The server is published to npm and runs with npx — there is nothing to install or host. Replace ei_live_xxxxxxxxx with your own key throughout. It supports two transports: stdio (default, runs locally) and HTTP.

Stdio (default)

HTTP transport

Run the server over HTTP for remote or web-based integrations. In HTTP mode each client authenticates by passing its API key as a Bearer token. Start the server:
It listens on http://127.0.0.1:3000 and exposes the MCP endpoint at /mcp using Streamable HTTP.

Options

The MCP server is a thin client over the REST API — all access control, org-scoping and rate limits are enforced by the API itself. A key used here has the same read-only access it does everywhere.