Skip to main content
Glama

Related Servers

Alternatives to admentum-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants and agents to Finland's school system, enabling retrieval of schedules, homework, exams, grades, messages, absences, and related school information for all of a family's children across multiple accounts. It runs locally, logs in only to the school service, and cannot send messages or change data.
      2
      20
      89
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Runs locally and lets AI clients read course deadlines, courses, announcements, activities, and files through a user-authenticated browser session, with assignment submission optional.
      6
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to read a student's own UGent Ufora (D2L Brightspace) data, including courses, announcements, deadlines, grades, course materials, and PDF text, over stdio or local Streamable HTTP. All operations are read-only and run locally against the student's authenticated session.
      19
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables reading Skoleplattform Oslo messages and downloading attachments through a local read-only MCP server, with tools to list messages, read a message, and download an attachment. It does not send replies or mark messages as read.
      3
      4
      BSD Zero Clause
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to search and read institutional IMAP mailboxes, download attachments, mark messages read or unread, move them between folders, and save drafts, all safely by UID. Runs locally over stdio or as a remote HTTP/SSE endpoint secured by a bearer token for clients like ChatGPT and n8n.
      6
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct scope: sync fetches new messages, status reports health, list_pending and list_threads summarize different views, and search vs grep_item differ by global vs single-item scope. The attachment tools are explicitly separated by use case (full item, long-text slice, image/PDF page), so misselection risk is low.

    Naming Consistency4/5

    Most names follow a verb_noun pattern (get_item, list_pending, get_attachment_text, mark_seen), with a few bare names (sync, search, prune, status) and one noun. The pattern is readable and all lowercase snake_case, but not perfectly uniform.

    Tool Count5/5

    Twelve tools is well within the 3-15 sweet spot and each covers a distinct part of the sync/read/maintenance workflow. No tool feels redundant or missing at this scope.

    Completeness4/5

    The surface covers sync, discovery, full-text search, item and attachment reading, thread context, marking seen, pruning, and status health. Minor gaps exist for a fuller message client, such as no send/reply or rule management despite rule counts, but core agent workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues