Skip to main content
Glama
asgard-ai-platform

mcp-mayo

Related Servers

Alternatives to mcp-mayo

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the HR platform 'МояКоманда' that enables AI assistants to access and interact with HR data like employees, teams, calendar, absences, requests, knowledge base, surveys, and more via its REST API.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that lets AI models interact with Oracle Fusion Cloud HCM across its entire REST surface. It uses generic, schema-aware tools to dynamically discover licensed modules and resources without per-endpoint code.
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying employee data via tools like get_employees and get_employee_by_id. Serves as a proof-of-concept for integrating Pega applications with AI agents.
      5 npm
      ISC
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with an HR database, enabling querying employee data and HR operations via natural language.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes HR business tools — attendance, payroll, organization, and recruiting — as native tools that AI models can call. Connections are secured via MCP OAuth 2.0 (discovery, dynamic client registration, authorization code with PKCE, refresh token rotation), static bearer tokens, or anonymous access.
      19 npm
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 33 tools

    Disambiguation2/5

    Several tool pairs have unclear boundaries, such as list_active_employees vs search_active_employees, get_salary_bonus_list vs get_monthly_payroll_report, and export_employees vs export_employees_full. While descriptions attempt to differentiate them, the overlap makes it easy for an agent to select the wrong tool.

    Naming Consistency3/5

    Most tools follow a snake_case verb_noun pattern, but the verbs are inconsistent: list, get, search, and export are used interchangeably without a clear rule. For example, list_active_employees and search_active_employees both exist, and get_ vs export_ prefixes are used for similar data.

    Tool Count2/5

    With 33 tools, the server is well beyond the typical 3-15 range. Although the HR domain is broad, many tools are redundant or could be consolidated, such as the multiple export variants and monthly insurance getters, making the count feel excessive.

    Completeness4/5

    The server covers a wide range of HR data including employees, organization, attendance, leave, salary, insurance, and expatriation. Composite tools like get_employee_profile and get_attendance_summary fill gaps, though write operations are absent, which is acceptable for a reporting-focused server.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive