Skip to main content
Glama
MyAmrita_MCP

MyAmrita_MCP

Amrita AI Assistant

A personal MCP server that lets an AI assistant (Claude, ChatGPT, etc.) read data from the Amrita Vishwa Vidyapeetham student portal (students.amrita.edu) on your behalf — attendance, timetable, marks, and more — using your own logged-in session.

Built on NitroStack (typescript-starter template).

What This Includes

  • auth module — captures and persists a Microsoft SSO-backed portal session

  • attendance module — attendance_get_attendance, attendance_get_low_attendance_subjects

  • More modules tracked as issues on this repo, built one at a time

Related MCP server: hello-mcp

Setup

npm install
cp .env.example .env

Generate a real value for SESSION_ENCRYPTION_KEY in .env:

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Logging In

The portal's login is federated through Microsoft Entra ID (Microsoft SSO) — there's no username/password form to automate directly, and the MCP client host (e.g. NitroStudio) often can't display a browser window itself. So logging in is a two-step, semi-manual process:

1. Launch a debuggable browser yourself, in your own terminal:

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --remote-debugging-port=9222 --user-data-dir="%TEMP%\amrita-edge-profile"

Leave that Edge window open.

2. Call the auth_login tool (from NitroStudio, or any MCP client connected to this server). It connects to that already-open browser, navigates it to the Amrita SSO login page, and waits (up to 5 minutes) for you to sign in yourself — including any MFA step. Once you land back on the portal dashboard, the resulting session is captured and persisted (encrypted, to .amrita-session.enc) so every other tool reuses it automatically until the portal session itself expires. Re-run auth_login (with the Edge window open again) whenever auth_status reports authenticated: false.

auth_logout clears the locally stored session.

Common Commands

npm run dev     # start in development mode (STDIO transport)
npm run build   # compile TypeScript + bundle widgets
npm start       # build and run the production server

Testing with NitroStudio

NitroStudio is the recommended way to inspect and manually test tools during development: open it, point it at this project folder, and use the Tools page to execute tools, inspect input schemas, and view JSON output.

Manual auth test script

scripts/manual-auth-test.mjs connects to the built server directly over stdio with a generous per-call timeout, useful for testing auth_login end-to-end outside of NitroStudio:

npm run build
node scripts/manual-auth-test.mjs

Widgets

Tool results render responsive widgets with light/dark host themes. Build using npm run build; NitroStack emits self-contained HTML in src/widgets/out. Each page includes the shared shell because production bundling bypasses the Next.js layout.

Validation: npm run typecheck:widgets and, after building, npm run test:widgets. Browser tests use synthetic data and block network access. They use installed Edge by default; set WIDGET_BROWSER=chromium when using Playwright Chromium. No portal login is required. See widget plan for delivery scope.

Available Tools

3 tools
auth_loginA

Open a real browser window for the user to log in to the Amrita student portal via Microsoft SSO. Only call this after the user has explicitly asked to log in or re-authenticate — it opens a visible browser window and blocks until the user finishes signing in themselves (or times out after 5 minutes). Once logged in, the session is reused automatically by every other tool until it expires.

Inputs: no named parameters.

auth_logoutA

Clear the locally stored Amrita portal session.

Inputs: no named parameters.

auth_statusA

Check whether there is currently a valid, active session with the Amrita student portal.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool covers a distinct lifecycle step: status checks the session, login initiates it, and logout terminates it. There is no semantic overlap or ambiguity between the three tools.

    Naming Consistency4/5

    All tools share the auth_ prefix and use snake_case, so the naming is mostly consistent. However, auth_status is a noun-like command while auth_login and auth_logout are verb-like, so a name like get_auth_status would be more uniform.

    Tool Count4/5

    Three tools is a reasonable size for an authentication submodule, and each tool earns its place. Given the server name MyAmrita_MCP, the count feels slightly under-scoped if the server is intended to cover the full student portal experience.

    Completeness2/5

    The authentication lifecycle itself is complete, but there are no tools to access or act on any Amrita portal data. Since the descriptions imply the session is meant to be reused by other tools, the absence of any portal-facing tools creates significant gaps that will cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers