HSE SmartLMS and personal account

io.github.ihavealotofguapPublished by GitHub account ihavealotofguapv0.1.2Updated Nov 6, 2026

HSE University (NIU VShE) SmartLMS and personal account (lk.hse.ru) via browser SSO

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Local MCP server that signs an assistant into HSE University's SmartLMS and personal account (lk.hse.ru) through browser SSO.

What you can do
  • Sign in to HSE SmartLMS and the lk.hse.ru personal account via browser SSO.
  • Read data from SmartLMS and the personal account with the default, read-only tool set.
  • Optionally submit data to SmartLMS and ELK, but only when write tools are explicitly enabled.
When to use it
Useful for HSE University students or staff who want an assistant to pull information from SmartLMS and their personal account, and optionally submit coursework-related data, without leaving the chat.
Requirements
Runs as a local process over stdio, installed from the npm package hse-mcp; desktop only. Needs an HSE login in HSE_EMAIL and the account password in HSE_PASSWORD, or stored in the system keychain via the credentials command. Write tools stay off unless HSE_ENABLE_WRITES is set to true.
Before you install
Requires your real HSE account password, which the server uses to sign in through browser SSO; prefer storing it in the system keychain over a plain environment variable. Setting HSE_ENABLE_WRITES to true lets the assistant submit data to SmartLMS and ELK, so leave it off unless you intend writes. Only works with HSE University accounts.

Installation

In SourceWeft

  1. Open HSE SmartLMS and personal account in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.2LatestOct 29, 2026
  2. v0.1.1Oct 26, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts