MyAmrita_MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NITRO_MCP_PROTOCOL_VERSION | No | MCP protocol version to serve. Defaults to 'auto' (serve both modern and legacy). | auto |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether there is currently a valid, active session with the Amrita student portal. |
| 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. |
| auth_logoutA | Clear the locally stored Amrita portal session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Health Checks | Current health status of all registered health checks |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
TDQS
Scored across 3 tools
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.
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.
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.
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.