eClass MCP Server

What is eClass MCP Server?

An MCP server for interacting with the Open eClass platform, with support for UoA’s CAS SSO authentication. It provides tools for logging in, retrieving enrolled courses, and managing sessions through the Model Context Protocol.

How to use eClass MCP Server?

Install Python 3.10+ and uv (or pip), clone the repository, run uv sync --dev --all-extras, create a .env file with ECLASS_USERNAME and ECLASS_PASSWORD, then execute python run_server.py. For MCP clients, configure the server path and set the required environment variables in the client’s MCP configuration.

Key features of eClass MCP Server

• SSO authentication through UoA’s CAS system
• Retrieve list of enrolled courses
• Persistent sessions between tool calls
• Verify authentication status
• Credentials stored locally in .env only

Use cases of eClass MCP Server

• Log into Open eClass via UoA SSO
• Retrieve your enrolled courses
• Check if you are currently authenticated
• End a session securely

FAQ from eClass MCP Server

What authentication method does eClass MCP Server support?

It supports UoA’s CAS SSO system for login.

What are the system requirements?

Python 3.10+ and either uv (recommended) or pip.

Where are credentials stored and are they exposed to AI providers?

Credentials are stored in a local .env file and are never passed as tool parameters, preventing exposure to AI providers.

Does the server store any data externally?

No. Sessions are maintained only in-memory, and no cloud services or remote storage are used.

What tools does the server provide?

Four tools: login, get_courses, logout, and authstatus. All require a dummy random_string parameter as an MCP protocol requirement.