The hosted MCP server
ClassQuill runs a hosted MCP server at:equateit-mcp npm
package, but hosted for you as a remote Streamable HTTP endpoint — so any
AI tool can connect over the network without installing anything. It is a thin
proxy to the ClassQuill public API: all access control,
org-scoping and rate limits are enforced by the API itself.
There are two ways to authenticate, depending on the client:
Both paths reach the same read-only tools. OAuth exists because claude.ai’s
custom connectors require it; everywhere else, a plain API key is simpler.
Create a key in Settings → Developers (org admins only) — see
Authentication.
Claude (claude.ai custom connector — OAuth)
claude.ai connects through OAuth, so there is no key to paste — you authorise ClassQuill the same way you would any other app.1
Open connector settings
In claude.ai, go to Settings → Connectors → Add custom connector.
2
Enter the MCP URL
Set the URL to
https://mcp.classquill.com/mcp and add the connector.3
Complete the login
Claude discovers the OAuth server automatically and opens a ClassQuill login.
Sign in and approve access. Claude registers itself, runs PKCE, and stores
the token — the connector’s tools then appear in your tool list.
401 with a WWW-Authenticate header pointing
at the server’s protected-resource metadata
(/.well-known/oauth-protected-resource/mcp), which names the authorisation
server (api.classquill.com). Claude then does Dynamic Client Registration and
an authorization-code + PKCE flow. This is all automatic — you only click
Log in.
Custom connectors are available on claude.ai paid plans. Claude Code connects
differently — see Claude Code below.
Codex
Add the hosted server to your Codex MCP configuration with your API key as a Bearer token. Replaceei_live_xxxxxxxxx with your own key.
Composio
In Composio, add a custom MCP server pointing at the hosted URL and set the authorization header to your API key.Claude Code
Claude Code connects to the hosted endpoint over HTTP with your API key in theAuthorization header — no OAuth needed.
Any other MCP client
Any client that speaks Streamable HTTP MCP can connect by sending your key as a Bearer token on each request:Prefer to run it yourself?
If you would rather run the server locally (stdio, or your own HTTP host) instead of using the hosted endpoint, use theequateit-mcp npm package
— same tools, same read-only access.
Every connector here is read-only and scoped to the organisation that owns
the key or OAuth session, exactly like the REST API. A key
used here has the same access it does everywhere, and the same
rate limits apply.