Skip to main content
Glama
tixuz

openemis-mcp

by tixuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to openemis-mcp

No user-submitted related servers found.

    Related Servers

    • openemis-mcp-pro

      tixuz
      A
      license
      A
      quality
      D
      maintenance
      A read/write MCP server that connects AI assistants to the OpenEMIS school management system, allowing natural-language queries and write operations across 678 resources and 3361 endpoints.
      12
      27 npm
      2
      MIT

    • SchoolBridge

      NSK-394
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to safely query and act on school data (attendance, fees, student records) with strict role-based access control and a two-step write approval flow.
      -

    • Crescender MCP Server

      lincalinca
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server that connects AI clients to Crescender's school asset, loan, member, and asset-comms API.
      6
      MIT

    • College AI Assistant

      Abhi122005
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides MCP tools for searching student profiles, viewing marks/attendance, and finding low-attendance students. Enables AI assistants like Gemini to interact with college student data through natural language.
      -

    • skyward-mcp

      caleb-media-studio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables students and educators to connect ChatGPT, Claude, or another MCP client to the Skyward account they are already authorized to use, through a self-hosted deployment they control. It exposes read-only tools for report cards, gradebooks, academic history, attendance, schedules, test scores, fees, and graduation requirements.
      4 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health check, generic data fetch, domain listing, topic discovery, playbook listing, and playbook details. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow the consistent 'openemis_' prefix with snake_case names (health, get, list_domains, discover, list_playbooks, get_playbook), providing a clear and predictable pattern.

    Tool Count5/5

    With 6 tools covering health, data retrieval, domain exploration, and playbook access, the count is well-scoped for a focused integration without being too sparse or bloated.

    Completeness4/5

    The tool set provides comprehensive read access via openemis_get and discovery tools, but lacks write operations (create, update, delete). For a read-oriented server this is acceptable, though adding CRUD would improve completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources