agoraplus-saintmaur-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGORAPLUS_SESSION_COOKIE | No | Session cookie for authenticated access to Agora Plus. Optional; required only if accessing authenticated endpoints. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| portal_infoA | Return non-sensitive portal metadata and the supported read-only scope. |
| initial_configB | Read the public/portal configuration without exposing credentials. |
| start_loginA | Open a persistent Chromium profile for a manual Agora Plus login. |
| session_statusA | Report whether the persistent browser session appears authenticated. |
| peri_inscriptionsA | Read current peri-school inscriptions through the authenticated browser session. No reservation or cancellation is made. The payload format is portal-version dependent and must be captured from an authenticated session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: portal_info and initial_config expose metadata/config, start_login and session_status handle authentication, and peri_inscriptions reads data. There is no overlap or ambiguity between them.
Names are readable and snake_case, but they mix noun phrases (portal_info, initial_config) with verb-led commands (start_login) and state descriptors (session_status). This is a mild inconsistency, though still predictable due to the small set.
With 5 tools, the server is well-scoped around portal metadata, configuration, authentication, and data reading. This is an appropriate size for a focused MCP server.
The surface covers the full read-only workflow: config, login, session check, and data retrieval. Minor gaps exist, such as a logout tool or explicit session refresh, but these are not blocking for the stated read-only scope.