Skip to main content
Glama
tixuz

openemis-mcp-pro

by tixuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to openemis-mcp-pro

No user-submitted related servers found.

    Related Servers

    • SchoolBridge

      NSK-394
      F
      license
      Not graded
      quality
      C
      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.
      -

    • yt-mcp-server-odoo

      yugmatech
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Odoo ERP, allowing natural language queries, record creation, updates, and deletions.
      LGPL 3.0

    • fast-odoo-mcp

      hjdhnx
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI assistants to interact with Odoo ERP systems, allowing natural language access to business data, CRUD operations, and instance management without requiring Odoo module installation.
      1
      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.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health check, login/logout/whoami for session management, CRUD operations, discovery and playbook tools for exploration. No overlaps or ambiguous boundaries.

    Naming Consistency5/5

    All tools follow the consistent 'openemis_verb_or_noun' pattern (e.g., openemis_get, openemis_create, openemis_login, openemis_list_domains). Names are predictable and descriptive.

    Tool Count5/5

    12 tools is a well-scoped number for an API client covering authentication, CRUD, discovery, and playbooks. Each tool earns its place without being excessive or insufficient.

    Completeness5/5

    The tool surface covers the full lifecycle: health check, user login/logout/whoami, CRUD operations, and domain/playbook discovery. Batch fetching and filtering are supported via openemis_get, and workflow-controlled resources are handled via playbook tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources